From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
qyousef@layalina.io
Subject: Re: [PATCH v2] sched/fair: Fix wakeup_preempt_fair for not waking up task
Date: Mon, 4 May 2026 12:02:17 +0200 [thread overview]
Message-ID: <20260504100217.GS3126523@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260503104503.1732682-1-vincent.guittot@linaro.org>
On Sun, May 03, 2026 at 12:45:03PM +0200, Vincent Guittot wrote:
> The assumption that p is always enqueued and not delayed, is only true for
> wakeup. If p was moved while delayed, pick_next_entity will dequeue it
> and the cfs might become empty. Test if there are still queued tasks
> before trying again to determine if p could be the next one to be picked.
>
> There are at least 2 cases:
>
> When cfs becomes idle, it tries to pull tasks but if those pulled tasks are
> delayed, they will be dequeued when attached to cfs.
> attach_tasks() -> attach_task() -> wakeup_preempt(rq, p, 0);
>
> A misfit task running on cfs A triggers a load balance to be pulled on a
> better cpu, the load balance on cfs B starts an active load balance to
> pulled the running misfit task. If there is a delayed dequeue task on cfs A
> , it can be pulled instead of the previously running misfit task.
> attach_one_task() -> attach_task() -> wakeup_preempt(rq, p, 0);
>
> Fixes: ac8e69e69363 ("sched/fair: Fix wakeup_preempt_fair() vs delayed dequeue")
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
>
> Change since v1:
> - Use cfs_rq->nr_queued instead of WF_TTWU flag to cover all cases instead
> of just wakeup.
>
> I'm preparing patches to cover those useless newly idle and active load
> balance task migration.
>
> kernel/sched/fair.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 728965851842..24087b0f25f6 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -9145,9 +9145,10 @@ static void wakeup_preempt_fair(struct rq *rq, struct task_struct *p, int wake_f
>
> /*
> * Because p is enqueued, nse being null can only mean that we
> - * dequeued a delayed task.
> + * dequeued a delayed task. If there are still entities queued in
> + * cfs, check if the next one will be p.
> */
> - if (!nse)
> + if (!nse && cfs_rq->nr_queued)
> goto pick;
>
> if (sched_feat(RUN_TO_PARITY))
Right, that works. Thanks!
next prev parent reply other threads:[~2026-05-04 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-03 10:45 [PATCH v2] sched/fair: Fix wakeup_preempt_fair for not waking up task Vincent Guittot
2026-05-04 10:02 ` Peter Zijlstra [this message]
2026-05-05 10:50 ` [tip: sched/urgent] sched/fair: Fix wakeup_preempt_fair() " tip-bot2 for Vincent Guittot
2026-05-05 14:13 ` tip-bot2 for Vincent Guittot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260504100217.GS3126523@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox