Re: [PATCH 2/2] sched_ext: Block a retained donor before PI deboost routes it back to sched_ext
From: Peter Zijlstra
Date: Thu Nov 12 2026 - 11:49:28 EST
On Thu, Nov 12, 2026 at 05:05:04PM +0100, Andrea Righi wrote:
> To recap, we ran into this while developing the proxy-exec support for
> scx. Earlier versions were handling the PI deboost case too and we also
> explored passing next_class into sched_change_begin(). But that didn't
> make it into the final version and it was left as a future improvement,
> to keep things simpler.
> Would it make sense to revisit the old idea passing next_class into
> sched_change_begin(), so we can handle entry into EXT consistently
> before recording the queued/running state and replace the separate
> class-entry preparation hooks?
As per my follow up email, I think all we need is for the existing
switching_to callback to return a boolean to indicate if the class is
willing to accept blocked tasks.