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.15] sched_ext: Event counter updates
Date: Fri, 7 Feb 2025 22:42:14 -1000 [thread overview]
Message-ID: <20250208084229.1274399-1-tj@kernel.org> (raw)
Hello,
This patchset contains the following three event counter updates:
0001-tool-sched_ext-Event-counter-dumping-updates.patch
0002-sched_ext-Count-SCX_EV_DISPATCH_LOCAL_DSQ_OFFLINE-in.patch
0003-sched_ext-Add-SCX_EV_ENQ_SKIP_MIGRATION_DISABLED.patch
This patchset depends on two pending migration disabled handling patches on
top of sched_ext/for-614-fixes and the event counter addition in
sched_ext/for-6.15 and thus is on top of:
sched_ext/for-6.14-fixes
+ Two migration disabled handling update patches
http://lkml.kernel.org/r/Z6Zz79AUub1YuHwD@slm.duckdns.org
+ sched_ext/for-6.15
The following branch shows how these patches will be applied:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-evs
diffstat follows. Thanks.
kernel/sched/ext.c | 25 +++++++++++++++++++------
tools/sched_ext/scx_central.bpf.c | 21 ---------------------
tools/sched_ext/scx_qmap.bpf.c | 16 ++++++++--------
3 files changed, 27 insertions(+), 35 deletions(-)
--
tejun
next reply other threads:[~2025-02-08 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 8:42 Tejun Heo [this message]
2025-02-08 8:42 ` [PATCH 1/3] tool/sched_ext: Event counter dumping updates Tejun Heo
2025-02-08 8:42 ` [PATCH 2/3] sched_ext: Count SCX_EV_DISPATCH_LOCAL_DSQ_OFFLINE in the right spot Tejun Heo
2025-02-08 8:42 ` [PATCH 3/3] sched_ext: Add SCX_EV_ENQ_SKIP_MIGRATION_DISABLED Tejun Heo
2025-02-08 9:12 ` [PATCHSET sched_ext/for-6.15] sched_ext: Event counter updates Changwoo Min
2025-02-09 6:40 ` 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=20250208084229.1274399-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.