Lines Matching refs:preemption
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.
88 Note that you do not need to explicitly prevent preemption if you are holding
89 any locks or interrupts are disabled, since preemption is implicitly disabled
93 disabling preemption - any cond_resched() or cond_resched_lock() might trigger
95 reschedule. So use this implicit preemption-disabling property only if you
112 Notice how the preemption statements must encompass every reference of the
125 Preventing preemption using interrupt disabling
129 It is possible to prevent a preemption event using local_irq_disable and
131 an event that would set need_resched and result in a preemption check. When
132 in doubt, rely on locking or explicit preemption disabling.
137 These may be used to protect from preemption, however, on exit, if preemption
138 may be enabled, a test to see if preemption is required should be done. If
141 if they are ever called outside of this context, a test for preemption should
143 are also protected by preemption locks and so may use the versions which do
144 not check preemption.