diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2026-04-04 12:22:44 +0200 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2026-04-08 13:11:43 +0200 |
| commit | 14a857056466be9d3d907a94e92a704ac1be149b (patch) | |
| tree | d1e10a6e555ab6d08cd01505374c2f7aef0263ca /tools/perf/scripts/python | |
| parent | 591cd656a1bf5ea94a222af5ef2ee76df029c1d2 (diff) | |
sched/deadline: Use revised wakeup rule for dl_server
John noted that commit 115135422562 ("sched/deadline: Fix 'stuck' dl_server")
unfixed the issue from commit a3a70caf7906 ("sched/deadline: Fix dl_server
behaviour").
The issue in commit 115135422562 was for wakeups of the server after the
deadline; in which case you *have* to start a new period. The case for
a3a70caf7906 is wakeups before the deadline.
Now, because the server is effectively running a least-laxity policy, it means
that any wakeup during the runnable phase means dl_entity_overflow() will be
true. This means we need to adjust the runtime to allow it to still run until
the existing deadline expires.
Use the revised wakeup rule for dl_defer entities.
Fixes: 115135422562 ("sched/deadline: Fix 'stuck' dl_server")
Reported-by: John Stultz <jstultz@google.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Juri Lelli <juri.lelli@redhat.com>
Tested-by: John Stultz <jstultz@google.com>
Link: https://patch.msgid.link/20260404102244.GB22575@noisy.programming.kicks-ass.net
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions
