From: Sultan Alsawaf <sultan@kerneltoast.com>
To: Xuewen Yan <xuewen.yan94@gmail.com>
Cc: Stephan Gerhold <stephan.gerhold@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 1/2] cpufreq: schedutil: Fix superfluous updates caused by need_freq_update
Date: Wed, 9 Apr 2025 19:22:33 -0700 [thread overview]
Message-ID: <Z_cracmQRfB8hF06@sultan-box.localdomain> (raw)
In-Reply-To: <CAB8ipk8AAFFtV3OA4S=g9X9AXsC4Ntr911DLLRkhgQtvMvXAvg@mail.gmail.com>
On Thu, Apr 10, 2025 at 10:13:04AM +0800, Xuewen Yan wrote:
> On Thu, Apr 10, 2025 at 10:09 AM Sultan Alsawaf <sultan@kerneltoast.com> wrote:
> >
> > On Thu, Apr 10, 2025 at 10:06:41AM +0800, Xuewen Yan wrote:
> > > On Thu, Apr 10, 2025 at 9:49 AM Sultan Alsawaf <sultan@kerneltoast.com> wrote:
> > > >
> > > > On Wed, Apr 09, 2025 at 07:48:05PM +0800, Xuewen Yan wrote:
> > > > > Or can we modify it as follows?
> > > > >
> > > > > -->8--
> > > > >
> > > > > diff --git a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> > > > > index 1a19d69b91ed..0e8d3b92ffe7 100644
> > > > > --- a/kernel/sched/cpufreq_schedutil.c
> > > > > +++ b/kernel/sched/cpufreq_schedutil.c
> > > > > @@ -83,7 +83,7 @@ static bool sugov_should_update_freq(struct
> > > > > sugov_policy *sg_policy, u64 time)
> > > > >
> > > > > if (unlikely(sg_policy->limits_changed)) {
> > > > > sg_policy->limits_changed = false;
> > > > > - sg_policy->need_freq_update =
> > > > > cpufreq_driver_test_flags(CPUFREQ_NEED_UPDATE_LIMITS);
> > > > > + sg_policy->need_freq_update = true;
> > > > > return true;
> > > > > }
> > > > >
> > > > > @@ -95,11 +95,15 @@ static bool sugov_should_update_freq(struct
> > > > > sugov_policy *sg_policy, u64 time)
> > > > > static bool sugov_update_next_freq(struct sugov_policy *sg_policy, u64 time,
> > > > > unsigned int next_freq)
> > > > > {
> > > > > - if (sg_policy->need_freq_update)
> > > > > + if (sg_policy->need_freq_update) {
> > > > > sg_policy->need_freq_update = false;
> > > > > - else if (sg_policy->next_freq == next_freq)
> > > > > - return false;
> > > > > + if (cpufreq_driver_test_flags(CPUFREQ_NEED_UPDATE_LIMITS))
> > > > > + goto change;
> > > > > + }
> > > > >
> > > > > + if (sg_policy->next_freq == next_freq)
> > > > > + return false;
> > > > > +change:
> > > > > sg_policy->next_freq = next_freq;
> > > > > sg_policy->last_freq_update_time = time;
> > > >
> > > > If CPUFREQ_NEED_UPDATE_LIMITS isn't specified, then there's no need to request a
> > > > frequency switch from the driver when the current frequency is exactly the same
> > > > as the next frequency.
> > >
> > > Yes, the following check would return false:
> > >
> > > + if (sg_policy->next_freq == next_freq)
> > > + return false;
> >
> > But what does that change fix? In fact, that change causes a limits update to
> > trigger a frequency switch request to the driver even when the new frequency is
> > the same as the current one.
>
> We set the sg_policy->need_freq_update = false instead of
> sg_policy->need_freq_update =
> cpufreq_driver_test_flags(CPUFREQ_NEED_UPDATE_LIMITS),
> to fix the original issue, and then add the
> + if (cpufreq_driver_test_flags(CPUFREQ_NEED_UPDATE_LIMITS))
> + goto change;
>
> to allow cpufreq to update when CPUFREQ_NEED_UPDATE_LIMITS is set.
Please take a closer look at this snippet in sugov_update_next_freq():
if (sg_policy->need_freq_update)
sg_policy->need_freq_update = false;
else if (sg_policy->next_freq == next_freq)
return false;
The 2nd if-statement is an else-if. Therefore, when need_freq_update is true, it
is set to false *and* skips the (sg_policy->next_freq == next_freq) check.
Sultan
next prev parent reply other threads:[~2025-04-10 2:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 1:57 [PATCH 2/2] cpufreq: schedutil: Ignore rate limit when scaling up with FIE present Sultan Alsawaf
2024-12-12 1:57 ` [PATCH 1/2] cpufreq: schedutil: Fix superfluous updates caused by need_freq_update Sultan Alsawaf
2024-12-12 13:24 ` Christian Loehle
2024-12-14 2:35 ` Sultan Alsawaf (unemployed)
2024-12-18 15:10 ` Rafael J. Wysocki
2025-04-08 8:59 ` Stephan Gerhold
2025-04-08 15:22 ` Sultan Alsawaf
2025-04-08 16:48 ` Stephan Gerhold
2025-04-09 11:25 ` Xuewen Yan
2025-04-09 11:48 ` Xuewen Yan
2025-04-10 1:49 ` Sultan Alsawaf
2025-04-10 2:06 ` Xuewen Yan
2025-04-10 2:08 ` Sultan Alsawaf
2025-04-10 2:13 ` Xuewen Yan
2025-04-10 2:22 ` Sultan Alsawaf [this message]
2025-04-10 2:30 ` Xuewen Yan
2025-04-10 2:33 ` Sultan Alsawaf
2025-04-10 2:42 ` Xuewen Yan
2025-04-10 1:52 ` Sultan Alsawaf
2025-04-10 19:16 ` Rafael J. Wysocki
2024-12-12 12:06 ` [PATCH 2/2] cpufreq: schedutil: Ignore rate limit when scaling up with FIE present Christian Loehle
2024-12-14 2:15 ` Sultan Alsawaf (unemployed)
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=Z_cracmQRfB8hF06@sultan-box.localdomain \
--to=sultan@kerneltoast.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=johan@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=stephan.gerhold@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan94@gmail.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