From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Use sched_energy_enabled()
Date: Fri, 27 Mar 2026 19:24:45 +0530 [thread overview]
Message-ID: <1d8050d1-39a7-4f6b-aa08-473cb8caf519@linux.ibm.com> (raw)
In-Reply-To: <20260327132013.2800517-1-vincent.guittot@linaro.org>
On 3/27/26 6:50 PM, Vincent Guittot wrote:
> Use helper sched_energy_enabled() everywhere we want to test if EAS is
> enabled instead of mixing sched_energy_enabled() and direct call to
> static_branch_unlikely().
>
> No functional change
>
Makes sense.
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
> kernel/sched/topology.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index 43150591914b..5847b83d9d55 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -273,7 +273,7 @@ void rebuild_sched_domains_energy(void)
> static int sched_energy_aware_handler(const struct ctl_table *table, int write,
> void *buffer, size_t *lenp, loff_t *ppos)
> {
> - int ret, state;
> + int ret;
>
> if (write && !capable(CAP_SYS_ADMIN))
> return -EPERM;
> @@ -289,8 +289,7 @@ static int sched_energy_aware_handler(const struct ctl_table *table, int write,
>
> ret = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
> if (!ret && write) {
> - state = static_branch_unlikely(&sched_energy_present);
> - if (state != sysctl_sched_energy_aware)
> + if (sysctl_sched_energy_aware != sched_energy_enabled())
> rebuild_sched_domains_energy();
> }
>
> @@ -388,11 +387,11 @@ static void destroy_perf_domain_rcu(struct rcu_head *rp)
>
> static void sched_energy_set(bool has_eas)
> {
> - if (!has_eas && static_branch_unlikely(&sched_energy_present)) {
> + if (!has_eas && sched_energy_enabled()) {
> if (sched_debug())
> pr_info("%s: stopping EAS\n", __func__);
> static_branch_disable_cpuslocked(&sched_energy_present);
> - } else if (has_eas && !static_branch_unlikely(&sched_energy_present)) {
> + } else if (has_eas && !sched_energy_enabled()) {
> if (sched_debug())
> pr_info("%s: starting EAS\n", __func__);
> static_branch_enable_cpuslocked(&sched_energy_present);
Acked-by: Shrikanth Hegde <sshegde@linux.ibm.com>
next prev parent reply other threads:[~2026-03-27 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 13:20 Vincent Guittot
2026-03-27 13:54 ` Shrikanth Hegde [this message]
2026-03-27 16:18 ` K Prateek Nayak
2026-03-27 16:32 ` Vincent Guittot
2026-03-27 17:09 ` K Prateek Nayak
2026-03-27 17:10 ` Dietmar Eggemann
2026-04-03 12:30 ` [tip: sched/core] " tip-bot2 for Vincent Guittot
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=1d8050d1-39a7-4f6b-aa08-473cb8caf519@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®