diff options
author | Frederic Weisbecker <fweisbec@gmail.com> | 2015-01-22 18:08:04 +0100 |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2015-01-30 19:38:51 +0100 |
commit | a18b5d01819235629289212ad428a5ee2b40f0d9 (patch) | |
tree | 9e3b0c3fdf4f9e994b13ee200cf32f5b2a311e88 /include/ras/ras_event.h | |
parent | 80e3d87b2c5582db0ab5e39610ce3707d97ba409 (diff) | |
download | op-kernel-dev-a18b5d01819235629289212ad428a5ee2b40f0d9.zip op-kernel-dev-a18b5d01819235629289212ad428a5ee2b40f0d9.tar.gz |
sched: Fix missing preemption opportunity
If an interrupt fires in cond_resched(), between the call to __schedule()
and the PREEMPT_ACTIVE count decrementation, and that interrupt sets
TIF_NEED_RESCHED, the call to preempt_schedule_irq() will be ignored
due to the PREEMPT_ACTIVE count. This kind of scenario, with irq preemption
being delayed because it's interrupting a preempt-disabled area, is
usually fixed up after preemption is re-enabled back with an explicit
call to preempt_schedule().
This is what preempt_enable() does but a raw preempt count decrement as
performed by __preempt_count_sub(PREEMPT_ACTIVE) doesn't handle delayed
preemption check. Therefore when such a race happens, the rescheduling
is going to be delayed until the next scheduler or preemption entrypoint.
This can be a problem for scheduler latency sensitive workloads.
Lets fix that by consolidating cond_resched() with preempt_schedule()
internals.
Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
Reported-by: Ingo Molnar <mingo@kernel.org>
Original-patch-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1421946484-9298-1-git-send-email-fweisbec@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'include/ras/ras_event.h')
0 files changed, 0 insertions, 0 deletions