Re: [PATCH 01/11] sched: Make NOHZ CFS bandwidth checks follow proxy donor
John Stultz <[email protected]> Fri, 17 Jul 2026 20:11:32 -0700
| Newsgroups | dev.linux.lists.sched-ext,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CANDhNCpiX7WB0XguQisf5u6Q6iJuFcNv6FiyO=mvWiOjHNoMoA@mail.gmail.com> |
On Thu, Jul 16, 2026 at 6:22 AM Andrea Righi <[email protected]> wrote: > > Proxy execution separates the scheduling context in rq->donor from the > physical execution context in rq->curr. sched_can_stop_tick() checks the > latter for CFS bandwidth constraints and only does so when nr_running is > one. > > A retained proxy donor keeps both the donor and mutex owner queued. The > check therefore misses a constrained FAIR donor and may stop the tick > while its runtime still needs to be enforced. > > Check the selected donor instead and remove the nr_running restriction. > The donor being a queued FAIR task is sufficient to require bandwidth > accounting regardless of other runnable tasks. > > Fixes: af0c8b2bf67b ("sched: Split scheduler and execution contexts") > Reported-by: Sashiko <[email protected]> > Link: https://lore.kernel.org/r/[email protected] > Signed-off-by: Andrea Righi <[email protected]> Acked-by: John Stultz <[email protected]>