From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Vincent Guittot <vincent.guittot@linaro.org>, <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>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/fair: Use sched_energy_enabled()
Date: Fri, 27 Mar 2026 21:48:16 +0530 [thread overview]
Message-ID: <458b21f7-6640-450c-889c-d05c6b0d801e@amd.com> (raw)
In-Reply-To: <20260327132013.2800517-1-vincent.guittot@linaro.org>
Hello Vincent,
On 3/27/2026 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
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
Feel free to include:
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
> ---
> 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())
Quick tangential question:
Since "sysctl_sched_energy_aware" is initialized to "1", if
build_perf_domains() returns false at boot, sysctl_sched_energy_aware
and sched_energy_enabled() will go out of sync and reading
"/proc/sys/kernel/sched_energy_aware" will still show "1" despite EAS
being disabled.
Is that okay?
Some sysctls like numa_balancing will show 0 if disabled (by user or
due to lack of NUMA) reflecting the real state of system. Should
sched_energy_aware do the same?
> rebuild_sched_domains_energy();
> }
>
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-03-27 16:18 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
2026-03-27 16:18 ` K Prateek Nayak [this message]
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=458b21f7-6640-450c-889c-d05c6b0d801e@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.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®