From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCHSET sched_ext/for-6.16] sched_ext: Unify idle CPU selection kfuncs
Date: Wed, 21 May 2025 09:34:05 +0200 [thread overview]
Message-ID: <20250521073548.140307-1-arighi@nvidia.com> (raw)
As discussed in [1], consolidate scx_bpf_select_cpu_dfl() and
scx_bpf_select_cpu_and(), allowing them to be called from the same contexts
and update the corresponding kselftest to reflect this change.
[1] https://lore.kernel.org/all/aCl1nq0hUJ7IdtC5@gpd3/
Andrea Righi (2):
sched_ext: idle: Consolidate default idle CPU selection kfuncs
selftests/sched_ext: Update test enq_select_cpu_fails
kernel/sched/ext_idle.c | 156 ++++++++++-----------
tools/testing/selftests/sched_ext/Makefile | 2 +-
.../selftests/sched_ext/enq_select_cpu.bpf.c | 74 ++++++++++
tools/testing/selftests/sched_ext/enq_select_cpu.c | 88 ++++++++++++
.../selftests/sched_ext/enq_select_cpu_fails.bpf.c | 43 ------
.../selftests/sched_ext/enq_select_cpu_fails.c | 61 --------
6 files changed, 234 insertions(+), 190 deletions(-)
create mode 100644 tools/testing/selftests/sched_ext/enq_select_cpu.bpf.c
create mode 100644 tools/testing/selftests/sched_ext/enq_select_cpu.c
delete mode 100644 tools/testing/selftests/sched_ext/enq_select_cpu_fails.bpf.c
delete mode 100644 tools/testing/selftests/sched_ext/enq_select_cpu_fails.c
next reply other threads:[~2025-05-21 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 7:34 Andrea Righi [this message]
2025-05-21 7:34 ` [PATCH 1/2] sched_ext: idle: Consolidate default idle CPU selection kfuncs Andrea Righi
2025-05-21 7:34 ` [PATCH 2/2] selftests/sched_ext: Update test enq_select_cpu_fails Andrea Righi
2025-05-21 17:36 ` [PATCHSET sched_ext/for-6.16] sched_ext: Unify idle CPU selection kfuncs 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=20250521073548.140307-1-arighi@nvidia.com \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).