Lines Matching refs:preemption

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
79 preemption is not enabled.
81 Note that you do not need to explicitly prevent preemption if you are holding
82 any locks or interrupts are disabled, since preemption is implicitly disabled
86 disabling preemption - any spin_unlock() decreasing the preemption count
88 So use this implicit preemption-disabling property only if you know that the
104 Notice how the preemption statements must encompass every reference of the
120 It is possible to prevent a preemption event using local_irq_disable and
122 an event that would set need_resched and result in a preemption check.  When
123 in doubt, rely on locking or explicit preemption disabling.
128 These may be used to protect from preemption, however, on exit, if preemption
129 may be enabled, a test to see if preemption is required should be done.  If
132 if they are ever called outside of this context, a test for preemption should
134 are also protected by preemption locks and so may use the versions which do
135 not check preemption.