From: Wyes Karny <wyes.karny@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ray.huang@amd.com, viresh.kumar@linaro.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
gautham.shenoy@amd.com
Subject: Re: [PATCH] cpufreq: amd-pstate: Update policy->cur for adjust perf
Date: Thu, 25 May 2023 11:43:39 +0530 [thread overview]
Message-ID: <ZG78k9dOJS2vauEP@BLR-5CG13462PL.amd.com> (raw)
In-Reply-To: <CAJZ5v0iR0tvS74s+EnzaSN-7urAWZGPgOEF4OTgaKgWNFueOgw@mail.gmail.com>
Hi Rafael,
On 24 May 19:57, Rafael J. Wysocki wrote:
> On Thu, May 18, 2023 at 7:58 AM Wyes Karny <wyes.karny@amd.com> wrote:
> >
> > Driver should update policy->cur after updating the frequency.
> > Currently amd_pstate doesn't update policy->cur when `adjust_perf`
> > is used. Which causes /proc/cpuinfo to show wrong cpu frequency.
> > Fix this by updating policy->cur with correct frequency value in
> > adjust_perf function callback.
> >
> > - Before the fix: (setting min freq to 1.5 MHz)
> >
> > [root@amd]# cat /proc/cpuinfo | grep "cpu MHz" | sort | uniq --count
> > 1 cpu MHz : 1777.016
> > 1 cpu MHz : 1797.160
> > 1 cpu MHz : 1797.270
> > 189 cpu MHz : 400.000
> >
> > - After the fix: (setting min freq to 1.5 MHz)
> >
> > [root@amd]# cat /proc/cpuinfo | grep "cpu MHz" | sort | uniq --count
> > 1 cpu MHz : 1753.353
> > 1 cpu MHz : 1756.838
> > 1 cpu MHz : 1776.466
> > 1 cpu MHz : 1776.873
> > 1 cpu MHz : 1777.308
> > 1 cpu MHz : 1779.900
> > 183 cpu MHz : 1805.231
> > 1 cpu MHz : 1956.815
> > 1 cpu MHz : 2246.203
> > 1 cpu MHz : 2259.984
> >
> > Fixes: 1d215f0319c2 ("cpufreq: amd-pstate: Add fast switch function for AMD P-State")
> >
> > Signed-off-by: Wyes Karny <wyes.karny@amd.com>
> > ---
> > drivers/cpufreq/amd-pstate.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> > index 5a3d4aa0f45a..736dab69ba1e 100644
> > --- a/drivers/cpufreq/amd-pstate.c
> > +++ b/drivers/cpufreq/amd-pstate.c
> > @@ -479,12 +479,14 @@ static void amd_pstate_adjust_perf(unsigned int cpu,
> > unsigned long capacity)
> > {
> > unsigned long max_perf, min_perf, des_perf,
> > - cap_perf, lowest_nonlinear_perf;
> > + cap_perf, lowest_nonlinear_perf, max_freq;
> > struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
> > struct amd_cpudata *cpudata = policy->driver_data;
> > + unsigned int target_freq;
> >
> > cap_perf = READ_ONCE(cpudata->highest_perf);
> > lowest_nonlinear_perf = READ_ONCE(cpudata->lowest_nonlinear_perf);
> > + max_freq = READ_ONCE(cpudata->max_freq);
> >
> > des_perf = cap_perf;
> > if (target_perf < capacity)
> > @@ -501,6 +503,10 @@ static void amd_pstate_adjust_perf(unsigned int cpu,
> > if (max_perf < min_perf)
> > max_perf = min_perf;
> >
> > + des_perf = clamp_t(unsigned long, des_perf, min_perf, max_perf);
> > + target_freq = div_u64(des_perf * max_freq, max_perf);
> > + policy->cur = target_freq;
> > +
> > amd_pstate_update(cpudata, min_perf, des_perf, max_perf, true,
> > policy->governor->flags);
> > cpufreq_cpu_put(policy);
> > --
>
> Applied under an edited subject, thanks!
>
> I think you'd like this to go into 6.4 and "stable", right?
Yes, please. I should have added stable tag.
Thanks & Regards,
Wyes
prev parent reply other threads:[~2023-05-25 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:58 Wyes Karny
2023-05-24 17:57 ` Rafael J. Wysocki
2023-05-25 6:13 ` Wyes Karny [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=ZG78k9dOJS2vauEP@BLR-5CG13462PL.amd.com \
--to=wyes.karny@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=viresh.kumar@linaro.org \
/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
Powered by JetHome