From: Tejun Heo <tj@kernel.org>
To: void@manifault.com, arighi@nvidia.com, multics69@gmail.com
Cc: linux-kernel@vger.kernel.org, sched-ext@meta.com
Subject: [PATCHSET sched_ext/for-6.18] sched_ext: Misc changes
Date: Tue, 2 Sep 2025 13:48:02 -1000 [thread overview]
Message-ID: <20250902234817.279206-1-tj@kernel.org> (raw)
A collection of four misc patches.
- Make scx_task_iter a bit easier to use.
- Keep bypass on between enable failure and disable.
- Move types and accessors into ext_internal.h.
- Wrap event percpu allocation in a struct to ease adding more percpu
fields.
0001-sched_ext-Make-explicit-scx_task_iter_relock-calls-u.patch
0002-sched_ext-Keep-bypass-on-between-enable-failure-and-.patch
0003-sched_ext-Move-internal-type-and-accessor-definition.patch
0004-sched_ext-Put-event_stats_cpu-in-struct-scx_sched_pc.patch
kernel/sched/build_policy.c | 1
kernel/sched/ext.c | 1097 +-----------------------------------------------------------------
kernel/sched/ext.h | 23 -
kernel/sched/ext_internal.h | 1064 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 1098 insertions(+), 1087 deletions(-)
--
tejun
next reply other threads:[~2025-09-02 23:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 23:48 Tejun Heo [this message]
2025-09-02 23:48 ` [PATCH 1/4] sched_ext: Make explicit scx_task_iter_relock() calls unnecessary Tejun Heo
2025-09-02 23:48 ` [PATCH 2/4] sched_ext: Keep bypass on between enable failure and scx_disable_workfn() Tejun Heo
2025-09-02 23:48 ` [PATCH 3/4] sched_ext: Move internal type and accessor definitions to ext_internal.h Tejun Heo
2025-09-03 10:32 ` Andrea Righi
2025-09-03 17:00 ` Tejun Heo
2025-09-03 20:52 ` Andrea Righi
2025-09-02 23:48 ` [PATCH 4/4] sched_ext: Put event_stats_cpu in struct scx_sched_pcpu Tejun Heo
2025-09-03 21:34 ` [PATCHSET sched_ext/for-6.18] sched_ext: Misc changes 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=20250902234817.279206-1-tj@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=multics69@gmail.com \
--cc=sched-ext@meta.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.