Searched refs:preemption (Results 1 – 25 of 46) sorted by relevance
12
| /Linux-v5.4/Documentation/ |
| D | preempt-locking.txt | 35 protect these situations by disabling preemption around them.
37 You can also use put_cpu() and get_cpu(), which will disable preemption.
44 Under preemption, the state of the CPU must be protected. This is arch-
47 section that must occur while preemption is disabled. Think what would happen
50 upon preemption, the FPU registers will be sold to the lowest bidder. Thus,
51 preemption must be disabled around such regions.
54 kernel_fpu_begin and kernel_fpu_end will disable and enable preemption.
72 Data protection under preemption is achieved by disabling preemption for the
84 n-times in a code path, and preemption will not be reenabled until the n-th
86 preemption is not enabled.
[all …]
|
| D | this_cpu_ops.txt | 20 necessary to disable preemption or interrupts to ensure that the
44 The following this_cpu() operations with implied preemption protection
46 preemption and interrupts::
111 reserved for a specific processor. Without disabling preemption in the
143 preemption has been disabled. The pointer is then used to
144 access local per cpu data in a critical section. When preemption
231 preemption. If a per cpu variable is not used in an interrupt context
|
| D | hwspinlock.txt | 95 Upon a successful return from this function, preemption is disabled so
111 Upon a successful return from this function, preemption and the local
127 Upon a successful return from this function, preemption is disabled,
178 Upon a successful return from this function, preemption is disabled so
195 Upon a successful return from this function, preemption and the local
211 Upon a successful return from this function, preemption is disabled,
268 Upon a successful return from this function, preemption and local
280 Upon a successful return from this function, preemption is reenabled,
|
| /Linux-v5.4/kernel/ |
| D | Kconfig.preempt | 10 This is the traditional Linux preemption model, geared towards
25 "explicit preemption points" to the kernel code. These new
26 preemption points have been selected to reduce the maximum
49 otherwise not be about to reach a natural preemption point.
|
| /Linux-v5.4/Documentation/core-api/ |
| D | local_ops.rst | 42 making sure that we modify it from within a preemption safe context. It is
76 preemption already disabled. I suggest, however, to explicitly
77 disable preemption anyway to make sure it will still work correctly on
104 local atomic operations: it makes sure that preemption is disabled around write
110 If you are already in a preemption-safe context, you can use
161 * preemptible context (it disables preemption) :
|
| /Linux-v5.4/Documentation/RCU/ |
| D | NMI-RCU.txt | 43 The do_nmi() function processes each NMI. It first disables preemption
48 preemption is restored.
92 CPUs complete any preemption-disabled segments of code that they were
94 Since NMI handlers disable preemption, synchronize_rcu() is guaranteed
|
| D | checklist.txt | 65 Disabling of preemption can serve as rcu_read_lock_sched(), but
217 or any pair of primitives that disables and re-enables preemption,
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-record_parse.txt | 41 The _tep_data_preempt_count()_ function gets the preemption count from the
64 preemption count.
95 /* Got the preemption count */
|
| D | libtraceevent-event_print.txt | 33 current context, and preemption count.
53 Field 4 is the preemption count.
|
| /Linux-v5.4/Documentation/virt/kvm/devices/ |
| D | arm-vgic.txt | 82 maximum possible 128 preemption levels. The semantics of the register
83 indicate if any interrupts in a given preemption level are in the active
86 Thus, preemption level X has one or more active interrupts if and only if:
90 Bits for undefined preemption levels are RAZ/WI.
|
| /Linux-v5.4/arch/arc/kernel/ |
| D | entry-compact.S | 152 ; if L2 IRQ interrupted a L1 ISR, disable preemption
157 ; -preemption off IRQ, user task in syscall picked to run
172 ; bump thread_info->preempt_count (Disable preemption)
367 ; decrement thread_info->preempt_count (re-enable preemption)
|
| D | entry.S | 292 ; --- (Slow Path #1) task preemption ---
|
| /Linux-v5.4/Documentation/arm/ |
| D | kernel_mode_neon.rst | 14 preemption disabled
58 * NEON/VFP code is executed with preemption disabled.
|
| /Linux-v5.4/include/rdma/ |
| D | opa_port_info.h | 356 } preemption; member
|
| /Linux-v5.4/Documentation/locking/ |
| D | ww-mutex-design.rst | 53 running transaction. Note that this is not the same as process preemption. A
350 The Wound-Wait preemption is implemented with a lazy-preemption scheme:
354 wounded status and retries. A great benefit of implementing preemption in
|
| /Linux-v5.4/Documentation/kernel-hacking/ |
| D | locking.rst | 16 With the wide availability of HyperThreading, and preemption in the
136 is set, then spinlocks simply disable preemption, which is sufficient to
137 prevent any races. For most purposes, we can think of preemption as
1138 these simply disable preemption so the reader won't go to sleep while
1241 Now, because the 'read lock' in RCU is simply disabling preemption, a
1242 caller which always has preemption disabled between calling
1304 preemption disabled. This also means you need to be in user context:
1393 preemption
1399 preemption, even on UP.
|
| D | hacking.rst | 65 Beware that if you have preemption or softirqs disabled (see below),
415 :c:func:`get_cpu()` disables preemption (so you won't suddenly get
422 interrupt context, or have preemption disabled) you can use
|
| /Linux-v5.4/Documentation/trace/ |
| D | tracepoints.rst | 100 the probe. This, and the fact that preemption is disabled around the
|
| D | ftrace.rst | 29 disabled and enabled, as well as for preemption and from a time
723 time for which preemption is disabled.
728 records the largest time for which irqs and/or preemption
1494 When preemption is disabled, we may be able to receive
1496 priority task must wait for preemption to be enabled again
1499 The preemptoff tracer traces the places that disable preemption.
1501 which preemption was disabled. The control of preemptoff tracer
1626 preemption disabled for the longest times is helpful. But
1627 sometimes we would like to know when either preemption and/or
1649 preemption is disabled. This total time is the time that we can
[all …]
|
| D | ftrace-uses.rst | 149 be called with preemption enabled (when CONFIG_PREEMPT is set),
|
| /Linux-v5.4/arch/m68k/ifpsp060/ |
| D | iskeleton.S | 261 | Linux/m68k: perhaps reenable preemption here...
|
| /Linux-v5.4/kernel/rcu/ |
| D | Kconfig | 77 only voluntary context switch (not preemption!), idle, and
|
| /Linux-v5.4/kernel/trace/ |
| D | Kconfig | 176 Enables hooks which will be called when preemption is first disabled,
186 Enable tracing of disable and enable events for preemption and irqs.
225 This option measures the time spent in preemption-off critical
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-design-CFS.rst | 200 process switch. This drives the running preemption.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | mmap.rst | 218 to random disk or network delays and preemption by other processes,
|
12
