From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: idle: Handle migration-disabled tasks in idle selection
Date: Thu, 17 Jul 2025 08:20:29 -1000 [thread overview]
Message-ID: <aHk-7UvELcnx8-wO@slm.duckdns.org> (raw)
In-Reply-To: <20250705054351.332038-1-arighi@nvidia.com>
On Sat, Jul 05, 2025 at 07:43:51AM +0200, Andrea Righi wrote:
> When SCX_OPS_ENQ_MIGRATION_DISABLED is enabled, migration-disabled tasks
> are also routed to ops.enqueue(). A scheduler may attempt to dispatch
> such tasks directly to an idle CPU using the default idle selection
> policy via scx_bpf_select_cpu_and() or scx_bpf_select_cpu_dfl().
>
> This scenario must be properly handled by the built-in idle policy to
> avoid returning an idle CPU where the target task isn't allowed to run.
> Otherwise, it can lead to errors such as:
>
> EXIT: runtime error (SCX_DSQ_LOCAL[_ON] cannot move migration disabled Chrome_ChildIOT[291646] from CPU 3 to 14)
>
> Prevent this by explicitly handling migration-disabled tasks in the
> built-in idle selection logic, maintaining their CPU affinity.
>
> Fixes: a730e3f7a48bc ("sched_ext: idle: Consolidate default idle CPU selection kfuncs")
> Signed-off-by: Andrea Righi <arighi@nvidia.com>
Applied to sched_ext/for-6.16-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2025-07-17 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 5:43 Andrea Righi
2025-07-17 18:20 ` Tejun Heo [this message]
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=aHk-7UvELcnx8-wO@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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®