From: Francesco Nigro <nigro.fra@gmail.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Mike Galbraith <efault@gmx.de>,
Mario Limonciello <mario.limonciello@amd.com>,
Huang Rui <ray.huang@amd.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [REPORT] sched: ITMT + DELAY_DEQUEUE: woken task waits ~1 ms behind another task on the preferred CPU while allowed CPUs are idle
Date: Thu, 5 Nov 2026 09:12:45 +0100 [thread overview]
Message-ID: <20261105081245.81773-1-nigro.fra@gmail.com> (raw)
In-Reply-To: <5af4860d-096a-4e9d-a3b3-0b8277924146@amd.com>
On Thu, 2026-11-05 at 09:41 +0530, K Prateek Nayak wrote:
> Hello Francesco,
Hi Prateek,
thanks a lot for looking into this, and for the patch.
This is a corporate machine, so I can't promise I will be able to boot
a patched kernel on it, but I will try.
> Since you say ITMT disabled actually solves this issue, I suspect there is a
> race between the idle balancer moving the delayed task to a preferred CPU vs
> a wakeup that also lands on the same CPU.
perf sched shows a race like that, but the task moved is the running
one, by active balance. One example (perf sched timehist, trimmed; ms):
.654334 [6] worker 482 awakened: migration/7
.654337 [6] worker 482 blocks
.654338 [7] worker 481 preempted while running
.654341 [7] migration/7 migrated: worker 481 cpu 7 => 6
.654341 [2] waker awakened: worker 482
.655572 [6] worker 482 ran 1.006 after 0.224 sch delay
Does your change cover the active balance path too?
> So at this point, I would have expected B to have already been
> moved by a newidle / idle balance.
Not here: in 270 of 286 waits of 0.5 ms or more, neither worker left
CPU 6, and CPUs 4, 5 and 7 were idle for at least 98 % of the wait.
Trace summary and excerpt:
https://github.com/franz1981/itmt-delay-dequeue-repro/tree/827b6b2
Thanks,
Franz
next prev parent reply other threads:[~2026-11-05 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 15:46 Francesco Nigro
2026-11-03 17:27 ` Mike Galbraith
2026-11-03 23:33 ` Francesco Nigro
2026-11-04 3:13 ` Mike Galbraith
2026-11-04 22:06 ` Francesco Nigro
2026-11-05 4:11 ` K Prateek Nayak
2026-11-05 8:12 ` Francesco Nigro [this message]
2026-11-05 8:34 ` K Prateek Nayak
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=20261105081245.81773-1-nigro.fra@gmail.com \
--to=nigro.fra@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ray.huang@amd.com \
--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
all inboxes | Powered by JetHome®