From: Yue Hu <zbestahu@gmail.com>
To: rafael@kernel.org
Cc: rjw@rjwysocki.net, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
huyue2@yulong.com, zbestahu@163.com, viresh.kumar@linaro.org
Subject: Re: [PATCH v2] cpufreq: schedutil: Call sugov_update_next_freq() before check to fast_switch_enabled
Date: Wed, 10 Mar 2021 19:20:51 +0800 [thread overview]
Message-ID: <20210310192051.00006659.zbestahu@gmail.com> (raw)
In-Reply-To: <20210224064727.w3w4b66jnsmcxdff@vireshk-i7>
Hi Rafael,
Please also review the patch.
I'm not sure if you have reviewed or not.
Thank you!
On Wed, 24 Feb 2021 12:17:27 +0530
Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 24-02-21, 14:39, Yue Hu wrote:
> > From: Yue Hu <huyue2@yulong.com>
> >
> > Note that sugov_update_next_freq() may return false, that means the
> > caller sugov_fast_switch() will do nothing except fast switch check.
> >
> > Similarly, sugov_deferred_update() also has unnecessary operations
> > of raw_spin_{lock,unlock} in sugov_update_single_freq() for that case.
> >
> > So, let's call sugov_update_next_freq() before the fast switch check
> > to avoid unnecessary behaviors above. Accordingly, update interface
> > definition to sugov_deferred_update() and remove sugov_fast_switch()
> > since we will call cpufreq_driver_fast_switch() directly instead.
> >
> > Signed-off-by: Yue Hu <huyue2@yulong.com>
> > ---
> > v2: remove sugov_fast_switch() and call cpufreq_driver_fast_switch()
> > directly instead, also update minor log message.
> >
> > kernel/sched/cpufreq_schedutil.c | 29 ++++++++++++-----------------
> > 1 file changed, 12 insertions(+), 17 deletions(-)
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
prev parent reply other threads:[~2021-03-10 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 6:39 Yue Hu
2021-02-24 6:47 ` Viresh Kumar
2021-03-10 11:20 ` Yue Hu [this message]
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=20210310192051.00006659.zbestahu@gmail.com \
--to=zbestahu@gmail.com \
--cc=huyue2@yulong.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=zbestahu@163.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®