From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH sched_ext/for-6.19] sched_ext: Fix build error in cgroup_set_idle()
Date: Mon, 13 Oct 2025 21:30:03 +0200 [thread overview]
Message-ID: <20251013193003.36215-1-arighi@nvidia.com> (raw)
Commit a5bd6ba30b336 ("sched_ext: Use cgroup_lock/unlock() to
synchronize against cgroup operations") renamed scx_cgroup_rwsem to
scx_cgroup_ops_rwsem.
Update cgroup_set_idle() accordingly to fix the resulting build error.
Fixes: d579dc6eb4fd0 ("sched/ext: Implement cgroup_set_idle() callback")
Signed-off-by: Andrea Righi <arighi@nvidia.com>
---
kernel/sched/ext.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index 228f4faef7670..430749ce46ab3 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -3217,7 +3217,7 @@ void scx_group_set_idle(struct task_group *tg, bool idle)
{
struct scx_sched *sch = scx_root;
- percpu_down_read(&scx_cgroup_rwsem);
+ percpu_down_read(&scx_cgroup_ops_rwsem);
if (scx_cgroup_enabled && SCX_HAS_OP(sch, cgroup_set_idle))
SCX_CALL_OP(sch, SCX_KF_UNLOCKED, cgroup_set_idle, NULL,
@@ -3226,7 +3226,7 @@ void scx_group_set_idle(struct task_group *tg, bool idle)
/* Update the task group's idle state */
tg->scx.idle = idle;
- percpu_up_read(&scx_cgroup_rwsem);
+ percpu_up_read(&scx_cgroup_ops_rwsem);
}
void scx_group_set_bandwidth(struct task_group *tg,
--
2.51.0
next reply other threads:[~2025-10-13 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 19:30 Andrea Righi [this message]
2025-10-14 20:28 ` [PATCH sched_ext/for-6.19] sched_ext: Fix build error in cgroup_set_idle() 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=20251013193003.36215-1-arighi@nvidia.com \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--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