Searched refs:preemption (Results 1 – 25 of 43) sorted by relevance
12
| /Linux-v4.19/Documentation/ |
| D | preempt-locking.txt | 36 protect these situations by disabling preemption around them.
38 You can also use put_cpu() and get_cpu(), which will disable preemption.
45 Under preemption, the state of the CPU must be protected. This is arch-
48 section that must occur while preemption is disabled. Think what would happen
51 upon preemption, the FPU registers will be sold to the lowest bidder. Thus,
52 preemption must be disabled around such regions.
55 kernel_fpu_begin and kernel_fpu_end will disable and enable preemption.
56 However, fpu__restore() must be called with preemption disabled.
74 Data protection under preemption is achieved by disabling preemption for the
86 n-times in a code path, and preemption will not be reenabled until the n-th
[all …]
|
| 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,
145 Upon a successful return from this function, preemption is disabled so
162 Upon a successful return from this function, preemption and the local
178 Upon a successful return from this function, preemption is disabled,
207 Upon a successful return from this function, preemption and local
219 Upon a successful return from this function, preemption is reenabled,
|
| 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
|
| /Linux-v4.19/kernel/ |
| D | Kconfig.preempt | 9 This is the traditional Linux preemption model, geared towards
24 "explicit preemption points" to the kernel code. These new
25 preemption points have been selected to reduce the maximum
48 otherwise not be about to reach a natural preemption point.
|
| /Linux-v4.19/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-v4.19/Documentation/RCU/ |
| D | NMI-RCU.txt | 43 The do_nmi() function processes each NMI. It first disables preemption
48 preemption is restored.
92 any preemption-disabled segments of code that they were executing.
93 Since NMI handlers disable preemption, synchronize_sched() is guaranteed
|
| D | checklist.txt | 65 Disabling of preemption can serve as rcu_read_lock_sched(), but
221 the corresponding readers must disable preemption, possibly
335 Similarly, disabling preemption is not an acceptable substitute
336 for rcu_read_lock(). Code that attempts to use preemption
|
| D | whatisRCU.txt | 929 and code segments with preemption disabled (whether
1030 Answer: Just as PREEMPT_RT permits preemption of spinlock
1031 critical sections, it permits preemption of RCU
|
| /Linux-v4.19/Documentation/virtual/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-v4.19/arch/arc/kernel/ |
| D | entry-compact.S | 155 ; if L2 IRQ interrupted a L1 ISR, disable preemption
160 ; -preemption off IRQ, user task in syscall picked to run
175 ; bump thread_info->preempt_count (Disable preemption)
370 ; decrement thread_info->preempt_count (re-enable preemption)
|
| D | entry.S | 295 ; --- (Slow Path #1) task preemption ---
|
| /Linux-v4.19/Documentation/arm/ |
| D | kernel_mode_neon.txt | 13 preemption disabled
57 * NEON/VFP code is executed with preemption disabled.
|
| /Linux-v4.19/include/rdma/ |
| D | opa_port_info.h | 354 } preemption; member
|
| /Linux-v4.19/Documentation/locking/ |
| D | ww-mutex-design.txt | 52 running transaction. Note that this is not the same as process preemption. A
343 The Wound-Wait preemption is implemented with a lazy-preemption scheme:
347 wounded status and retries. A great benefit of implementing preemption in
|
| /Linux-v4.19/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-v4.19/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
715 time for which preemption is disabled.
720 records the largest time for which irqs and/or preemption
1403 When preemption is disabled, we may be able to receive
1405 priority task must wait for preemption to be enabled again
1408 The preemptoff tracer traces the places that disable preemption.
1410 which preemption was disabled. The control of preemptoff tracer
1535 preemption disabled for the longest times is helpful. But
1536 sometimes we would like to know when either preemption and/or
1558 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-v4.19/arch/m68k/ifpsp060/ |
| D | iskeleton.S | 261 | Linux/m68k: perhaps reenable preemption here...
|
| /Linux-v4.19/kernel/trace/ |
| D | Kconfig | 175 Enables hooks which will be called when preemption is first disabled,
185 Enable tracing of disable and enable events for preemption and irqs.
224 This option measures the time spent in preemption-off critical
|
| /Linux-v4.19/kernel/rcu/ |
| D | Kconfig | 76 only voluntary context switch (not preemption!), idle, and
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | completion.txt | 134 interrupt context, with disabled irqs. or preemption is disabled - see also
|
| D | sched-design-CFS.txt | 194 process switch. This drives the running preemption.
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | mmap.rst | 211 to random disk or network delays and preemption by other processes,
|
12
