| /linux-4.4.14/Documentation/ |
| D | preempt-locking.txt | 32 protect these situations by disabling preemption around them.
34 You can also use put_cpu() and get_cpu(), which will disable preemption.
40 Under preemption, the state of the CPU must be protected. This is arch-
43 section that must occur while preemption is disabled. Think what would happen
46 upon preemption, the FPU registers will be sold to the lowest bidder. Thus,
47 preemption must be disabled around such regions.
50 kernel_fpu_begin and kernel_fpu_end will disable and enable preemption.
51 However, fpu__restore() must be called with preemption disabled.
67 Data protection under preemption is achieved by disabling preemption for the
77 n-times in a code path, and preemption will not be reenabled until the n-th
[all …]
|
| D | local_ops.txt | 33 sure that we modify it from within a preemption safe context. It is however
65 preemption already disabled. I suggest, however, to explicitly
66 disable preemption anyway to make sure it will still work correctly on
89 operations : it makes sure that preemption is disabled around write access to
95 If you are already in a preemption-safe context, you can use
145 * preemptible context (it disables preemption) :
|
| D | hwspinlock.txt | 71 Upon a successful return from this function, preemption is disabled so
83 Upon a successful return from this function, preemption and the local
95 Upon a successful return from this function, preemption is disabled,
106 Upon a successful return from this function, preemption is disabled so
117 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 and local
153 Upon a successful return from this function, preemption is reenabled,
|
| D | this_cpu_ops.txt | 16 necessary to disable preemption or interrupts to ensure that the
40 The following this_cpu() operations with implied preemption protection
42 preemption and interrupts.
107 reserved for a specific processor. Without disabling preemption in the
137 preemption has been disabled. The pointer is then used to
138 access local per cpu data in a critical section. When preemption
221 preemption. If a per cpu variable is not used in an interrupt context
|
| D | kprobes.txt | 133 or preemption), NR_CPUS should be enough. If maxactive <= 0, it is
559 Probe handlers are run with preemption disabled. Depending on the
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.preempt | 9 This is the traditional Linux preemption model, geared towards
23 "explicit preemption points" to the kernel code. These new
24 preemption points have been selected to reduce the maximum
46 otherwise not be about to reach a natural preemption point.
|
| /linux-4.4.14/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 | 55 Disabling of preemption can serve as rcu_read_lock_sched(), but
207 the corresponding readers must disable preemption, possibly
321 Similarly, disabling preemption is not an acceptable substitute
322 for rcu_read_lock(). Code that attempts to use preemption
|
| D | whatisRCU.txt | 905 and code segments with preemption disabled (whether
1005 Answer: Just as PREEMPT_RT permits preemption of spinlock
1006 critical sections, it permits preemption of RCU
|
| D | rcubarrier.txt | 307 Therefore, on_each_cpu() disables preemption across its call
|
| D | stallwarn.txt | 194 o A CPU looping with preemption disabled. This condition can
|
| D | RTFP.txt | 77 to preemption, excessive interrupts, or larger-than-anticipated load,
151 preemption of RCU realtime critical sections [PaulMcKenney05a,
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | arm-vgic.txt | 81 maximum possible 128 preemption levels. The semantics of the register
82 indicate if any interrupts in a given preemption level are in the active
85 Thus, preemption level X has one or more active interrupts if and only if:
89 Bits for undefined preemption levels are RAZ/WI.
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry-compact.S | 169 ; if L2 IRQ interrupted a L1 ISR, disable preemption
174 ; -preemption off IRQ, user task in syscall picked to run
189 ; bump thread_info->preempt_count (Disable preemption)
381 ; decrement thread_info->preempt_count (re-enable preemption)
|
| D | entry.S | 303 ; --- (Slow Path #1) task preemption ---
|
| /linux-4.4.14/Documentation/arm/ |
| D | kernel_mode_neon.txt | 13 preemption disabled
57 * NEON/VFP code is executed with preemption disabled.
|
| /linux-4.4.14/Documentation/locking/ |
| D | lglock.txt | 37 the lg_local_lock has to disable preemption as migration protection so
51 possible CPUs (including those off-line). The preemption disable/enable
|
| D | rt-mutex-design.txt | 89 algorithm. These locks disable preemption for UP (when
|
| /linux-4.4.14/include/rdma/ |
| D | opa_port_info.h | 369 } preemption; member
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 24 disabled and enabled, as well as for preemption and from a time
522 time for which preemption is disabled.
527 records the largest time for which irqs and/or preemption
1066 When preemption is disabled, we may be able to receive
1068 priority task must wait for preemption to be enabled again
1071 The preemptoff tracer traces the places that disable preemption.
1073 which preemption was disabled. The control of preemptoff tracer
1196 preemption disabled for the longest times is helpful. But
1197 sometimes we would like to know when either preemption and/or
1219 preemption is disabled. This total time is the time that we can
[all …]
|
| D | tracepoints.txt | 97 the probe. This, and the fact that preemption is disabled around the
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | iskeleton.S | 261 | Linux/m68k: perhaps reenable preemption here...
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 135 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-4.4.14/tools/perf/Documentation/ |
| D | perf-script.txt | 84 Show latency attributes (irqs/preemption disabled, etc).
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | compress_offload.txt | 220 hooks to query the utilization of the audio DSP, nor any preemption
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | entry.S | 608 # the preemption counter and if it is zero call preempt_schedule_irq
617 jnz .Lio_restore # preemption is disabled
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 43 to avoid preemption)
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 227 preemption. It is desireable that all irqchips in the GPIO subsystem keep this
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 740 premption||preemption
|
| /linux-4.4.14/arch/ |
| D | Kconfig | 434 rcu_irq_enter/rcu_irq_exit() but preemption or signal handling on
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp.txt | 154 highmem and preemption. It also has a extensible architecture that
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 201 This option measures the time spent in preemption-off critical
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | relay.txt | 423 __relay_write(), which only disables preemption. These functions
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 917 if kernel code uses it in a preemption-unsafe way. Also, the kernel
918 will detect preemption count underflows.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 527 only voluntary context switch (not preemption!), idle, and
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 4048 try that. An early version of the preemption patch and a 2.4.10 SuSE
|