Lines Matching full:preemption

88 The schedule called with preemption disabled (scpd) monitor ensures schedule is
89 called with preemption disabled::
110 does not enable preemption::
180 The need resched preempts (nrp) monitor ensures preemption requires
181 ``need_resched``. Only kernel preemption is considered, since preemption
184 A kernel preemption is whenever ``__schedule`` is called with the preemption
186 type of preemption occurs after the need for ``rescheduling`` has been set.
188 userspace preemption.
190 case, a task goes through the scheduler from a preemption context but it is
195 In theory, a preemption can only occur after the ``need_resched`` flag is set. In
196 practice, however, it is possible to see a preemption where the flag is not
206 In the situation above, standard preemption starts (e.g. from preempt_enable
209 When the preempted task runs again, the standard preemption started earlier
211 ``nested_preemption``, this allows another preemption without re-setting the
253 Due to how the ``need_resched`` flag on the preemption count works on arm64,
254 this monitor is unstable on that architecture, as it often records preemption
278   a task switch as a result of kernel preemption (``schedule_entry_preempt`` in
294 (e.g. due to preemption). However, it does include the event
296 can be triggered also by preemption, but cannot occur after the task got to
347 The operations with preemption and irq disabled (opid) monitor ensures
349 preemption disabled or during interrupt context, in such case preemption may
394 where the preemption tracepoints might not be visible, during interrupts
395 preemption is always disabled. On non- ``PREEMPT_RT`` kernels, the interrupts