aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/sctop.py
diff options
context:
space:
mode:
authorSebastian Andrzej Siewior <[email protected]>2019-08-16 16:06:26 +0000
committerIngo Molnar <[email protected]>2019-08-19 08:57:26 +0000
commitb0fdc01354f45d43f082025636ef808968a27b36 (patch)
treea4fea94cedf4d15223cc081ea367c47eb17bd2a6 /tools/perf/scripts/python/sctop.py
parentLinux 5.3-rc5 (diff)
downloadkernel-b0fdc01354f45d43f082025636ef808968a27b36.tar.gz
kernel-b0fdc01354f45d43f082025636ef808968a27b36.zip
sched/core: Schedule new worker even if PI-blocked
If a task is PI-blocked (blocking on sleeping spinlock) then we don't want to schedule a new kworker if we schedule out due to lock contention because !RT does not do that as well. A spinning spinlock disables preemption and a worker does not schedule out on lock contention (but spin). On RT the RW-semaphore implementation uses an rtmutex so tsk_is_pi_blocked() will return true if a task blocks on it. In this case we will now start a new worker which may deadlock if one worker is waiting on progress from another worker. Since a RW-semaphore starts a new worker on !RT, we should do the same on RT. XFS is able to trigger this deadlock. Allow to schedule new worker if the current worker is PI-blocked. Signed-off-by: Sebastian Andrzej Siewior <[email protected]> Cc: Linus Torvalds <[email protected]> Cc: Peter Zijlstra <[email protected]> Cc: Thomas Gleixner <[email protected]> Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/sctop.py')
0 files changed, 0 insertions, 0 deletions