summaryrefslogtreecommitdiffstats
path: root/debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch')
-rw-r--r--debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch2
1 files changed, 1 insertions, 1 deletions
diff --git a/debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch b/debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch
index 59baf9907..6ab901f02 100644
--- a/debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch
+++ b/debian/patches-rt/sched-core-Schedule-new-worker-even-if-PI-blocked.patch
@@ -1,7 +1,7 @@
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Wed, 29 May 2019 17:52:17 +0200
Subject: [PATCH] sched/core: Schedule new worker even if PI-blocked
-Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.2/older/patches-5.2.9-rt3.tar.xz
+Origin: https://www.kernel.org/pub/linux/kernel/projects/rt/5.2/older/patches-5.2.10-rt5.tar.xz
If a task is PI-blocked (blocking on sleeping spinlock) then we don't
schedule a new kworker if we schedule out due to lock contention because