From: Tejun Heo <tj@kernel.org>
To: sched-ext@lists.linux.dev
Cc: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
David Dai <david.dai@linux.dev>,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: [PATCHSET sched_ext/for-7.4-fixes] sched_ext: Fix ops.enqueue/dispatch() calls before ops.cpu_online()
Date: Sat, 31 Oct 2026 07:05:39 -1000 [thread overview]
Message-ID: <20261031170541.710939-1-tj@kernel.org> (raw)
Hello,
This patchset fixes ops.enqueue/dispatch() calls for a cpu before the root's
ops.cpu_online(). Both ops are gated on SCX_RQ_ONLINE, which follows the
core's rq online state, and on a runtime cpu up the sched domain rebuild in
sched_cpu_activate() puts the rq online before scx_rq_activate() calls
ops.cpu_online().
0002 tracks the flag in handle_hotplug() instead, set right after
ops.cpu_online() and cleared when the cpu goes down. 0001 is preparation.
Based on sched_ext/for-7.4-fixes (0aba89317f38).
This patchset contains the following 2 patches.
0001 sched_ext: Factor out drain_offline_rq()
0002 sched_ext: Fix ops.enqueue/dispatch() calls before ops.cpu_online()
The patchset is also available in the following git branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git cpu-online-order
diffstat follows. Thanks.
kernel/sched/ext/ext.c | 93 ++++++++++++++++++++++++++--------------------
kernel/sched/ext/inlines.h | 2 +-
kernel/sched/ext/sub.c | 9 +++--
kernel/sched/sched.h | 17 +++++----
4 files changed, 68 insertions(+), 53 deletions(-)
--
tejun
next reply other threads:[~2026-10-31 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 17:05 Tejun Heo [this message]
2026-10-31 17:05 ` [PATCH 1/2] sched_ext: Factor out drain_offline_rq() Tejun Heo
2026-10-31 17:05 ` [PATCH 2/2] sched_ext: Fix ops.enqueue/dispatch() calls before ops.cpu_online() Tejun Heo
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=20261031170541.710939-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=david.dai@linux.dev \
--cc=emil@etsalapatis.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®