From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
K Prateek Nayak <kprateek.nayak@amd.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.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 18:10:38 +0100 [thread overview]
Message-ID: <f67a03ae-a050-4118-8758-5ea60700a188@arm.com> (raw)
In-Reply-To: <CAKfTPtC33Ew3W=bq_GPr6xW+fxe05nHk=5_Pop13d3=Bi+73aw@mail.gmail.com>
On 27.03.26 17:32, Vincent Guittot wrote:
> On Fri, 27 Mar 2026 at 17:18, K Prateek Nayak <kprateek.nayak@amd.com> wrote:
>>
>> 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?
>
> Isn't the call to sched_is_eas_possible() there to prevent this case ?
Yes, I think so:
300 static const struct ctl_table sched_energy_aware_sysctls[] = {
...
302 .procname = "sched_energy_aware",
...
306 .proc_handler = sched_energy_aware_handler,
273 sched_energy_aware_handler()
...
281 if (!sched_is_eas_possible(cpu_active_mask)) { <-- !!!
282 if (write) {
283 return -EOPNOTSUPP;
284 } else {
285 *lenp = 0;
286 return 0;
287 }
...
# cat /proc/sys/kernel/sched_energy_aware
1
# ./set_cpufreq_ondemand.sh
cat /proc/sys/kernel/sched_energy_aware
[ 391.591167] rd 0-5: Checking EAS: cpufreq is not ready
Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
[...]
next prev parent reply other threads:[~2026-03-27 17:10 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
2026-03-27 16:32 ` Vincent Guittot
2026-03-27 17:09 ` K Prateek Nayak
2026-03-27 17:10 ` Dietmar Eggemann [this message]
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=f67a03ae-a050-4118-8758-5ea60700a188@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=bsegall@google.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®