From: "tip-bot2 for Michal Koutný" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: mkoutny@suse.com, "Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/rt: Move group schedulability check to sched_rt_global_validate()
Date: Wed, 08 Apr 2026 11:20:07 -0000 [thread overview]
Message-ID: <177564720734.801717.15872002446955322013.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20260323-sched-rert_groups-v3-2-1e7d5ed6b249@suse.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 4f70a0456d090303d5a6c915dd7d9db9da56cb16
Gitweb: https://git.kernel.org/tip/4f70a0456d090303d5a6c915dd7d9db9da56cb16
Author: Michal Koutný <mkoutny@suse.com>
AuthorDate: Mon, 23 Mar 2026 13:39:38 +01:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 08 Apr 2026 13:11:44 +02:00
sched/rt: Move group schedulability check to sched_rt_global_validate()
The sched_rt_global_constraints() function is a remnant that used to set
up global RT throttling but that is no more since commit 5f6bd380c7bdb
("sched/rt: Remove default bandwidth control") and the function ended up
only doing schedulability check.
Move the check into the validation function where it fits better.
(The order of validations sched_dl_global_validate() and
sched_rt_global_validate() shouldn't matter.)
Signed-off-by: Michal Koutný <mkoutny@suse.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://patch.msgid.link/20260323-sched-rert_groups-v3-2-1e7d5ed6b249@suse.com
---
kernel/sched/rt.c | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 893e54d..e16d8f1 100644
--- a/kernel/sched/rt.c
+++ b/kernel/sched/rt.c
@@ -2832,15 +2832,7 @@ long sched_group_rt_period(struct task_group *tg)
#ifdef CONFIG_SYSCTL
static int sched_rt_global_constraints(void)
{
- int ret = 0;
- if (!rt_group_sched_enabled())
- return ret;
-
- mutex_lock(&rt_constraints_mutex);
- ret = __rt_schedulable(NULL, 0, 0);
- mutex_unlock(&rt_constraints_mutex);
-
- return ret;
+ return 0;
}
#endif /* CONFIG_SYSCTL */
@@ -2872,6 +2864,13 @@ static int sched_rt_global_validate(void)
NSEC_PER_USEC > max_rt_runtime)))
return -EINVAL;
+#ifdef CONFIG_RT_GROUP_SCHED
+ if (!rt_group_sched_enabled())
+ return 0;
+
+ scoped_guard(mutex, &rt_constraints_mutex)
+ return __rt_schedulable(NULL, 0, 0);
+#endif
return 0;
}
next prev parent reply other threads:[~2026-04-08 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 12:39 [PATCH v3 0/3] sched/rt: Fix schedulable check with rt_group_sched=0 and cleanups Michal Koutný
2026-03-23 12:39 ` [PATCH v3 1/3] sched/rt: Skip group schedulable check with rt_group_sched=0 Michal Koutný
2026-04-08 11:20 ` [tip: sched/core] " tip-bot2 for Michal Koutný
2026-03-23 12:39 ` [PATCH v3 2/3] sched/rt: Move group schedulability check to sched_rt_global_validate() Michal Koutný
2026-04-08 11:20 ` tip-bot2 for Michal Koutný [this message]
2026-03-23 12:39 ` [PATCH v3 3/3] sched/rt: Cleanup global RT bandwidth functions Michal Koutný
2026-04-08 11:20 ` [tip: sched/core] " tip-bot2 for Michal Koutný
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=177564720734.801717.15872002446955322013.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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®