diff options
| author | Thomas Gleixner <tglx@linutronix.de> | 2021-09-23 18:54:44 +0200 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2021-10-01 13:57:51 +0200 |
| commit | 3e9cc688e56cc2abb9b6067f57c8397f6c96d42c (patch) | |
| tree | 71b840a99263940d42c5d3fbe357f42817e83813 /kernel/locking | |
| parent | 50e081b96e35e43b65591f40f7376204decd1cb5 (diff) | |
sched: Make cond_resched_lock() variants RT aware
The __might_resched() checks in the cond_resched_lock() variants use
PREEMPT_LOCK_OFFSET for preempt count offset checking which takes the
preemption disable by the spin_lock() which is still held at that point
into account.
On PREEMPT_RT enabled kernels spin/rw_lock held sections stay preemptible
which means PREEMPT_LOCK_OFFSET is 0, but that still triggers the
__might_resched() check because that takes RCU read side nesting into
account.
On RT enabled kernels spin/read/write_lock() issue rcu_read_lock() to
resemble the !RT semantics, which means in cond_resched_lock() the might
resched check will see preempt_count() == 0 and rcu_preempt_depth() == 1.
Introduce PREEMPT_LOCK_SCHED_OFFSET for those might resched checks and map
them depending on CONFIG_PREEMPT_RT.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20210923165358.305969211@linutronix.de
Diffstat (limited to 'kernel/locking')
0 files changed, 0 insertions, 0 deletions