From: "Gautham R. Shenoy" <gautham.shenoy@amd.com>
To: "Yuan, Perry" <Perry.Yuan@amd.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Ugwekar, Dhananjay" <Dhananjay.Ugwekar@amd.com>
Subject: Re: [PATCH 2/4] cpufreq/amd-pstate: Don't update CPPC request in amd_pstate_cpu_boost_update()
Date: Wed, 16 Oct 2024 15:20:08 +0530 [thread overview]
Message-ID: <Zw+MUOYw+nMuQ9Nk@BLRRASHENOY1.amd.com> (raw)
In-Reply-To: <CYYPR12MB865575C121660188BDD977B89C462@CYYPR12MB8655.namprd12.prod.outlook.com>
Hello Mario,
[..snip..]
> >
> > When boost is changed the CPPC value is changed in
> > amd_pstate_cpu_boost_update() but then changed again when
> > refresh_frequency_limits() and all it's callbacks occur. The first is a pointless write,
> > so instead just update the limits for the policy and let the policy refresh anchor
> > everything properly.
> >
> > Fixes: c8c68c38b56f ("cpufreq: amd-pstate: initialize core precision boost state")
> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> > ---
> > drivers/cpufreq/amd-pstate.c | 24 +-----------------------
> > 1 file changed, 1 insertion(+), 23 deletions(-)
> >
> > diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c index
> > dfa9a146769b..13dec8b1e7a8 100644
> > --- a/drivers/cpufreq/amd-pstate.c
> > +++ b/drivers/cpufreq/amd-pstate.c
> > @@ -665,34 +665,12 @@ static void amd_pstate_adjust_perf(unsigned int cpu,
> > static int amd_pstate_cpu_boost_update(struct cpufreq_policy *policy, bool on) {
> > struct amd_cpudata *cpudata = policy->driver_data;
> > - struct cppc_perf_ctrls perf_ctrls;
> > - u32 highest_perf, nominal_perf, nominal_freq, max_freq;
> > + u32 nominal_freq, max_freq;
> > int ret = 0;
> >
> > - highest_perf = READ_ONCE(cpudata->highest_perf);
> > - nominal_perf = READ_ONCE(cpudata->nominal_perf);
> > nominal_freq = READ_ONCE(cpudata->nominal_freq);
> > max_freq = READ_ONCE(cpudata->max_freq);
> >
> > - if (boot_cpu_has(X86_FEATURE_CPPC)) {
> > - u64 value = READ_ONCE(cpudata->cppc_req_cached);
> > -
> > - value &= ~GENMASK_ULL(7, 0);
> > - value |= on ? highest_perf : nominal_perf;
> > - WRITE_ONCE(cpudata->cppc_req_cached, value);
> > -
> > - wrmsrl_on_cpu(cpudata->cpu, MSR_AMD_CPPC_REQ, value);
So, for amd-pstate-epp driver
refresh_frequency_limits()
--> cpufreq_set_policy()
--> amd_pstate_epp_set_policy()
--> amd_pstate_epp_update_limit()
will ensure that the MSR is updated with the is updated with the
value after Patch 1.
> > - } else {
> > - perf_ctrls.max_perf = on ? highest_perf : nominal_perf;
> > - ret = cppc_set_perf(cpudata->cpu, &perf_ctrls);
refresh_frequency_limits()
--> cpufreq_start_governor()
--> governor->limits()
--> cpufreq_policy_apply_limits()
--> __cpufreq_driver_target()
--> amd_pstate_target()
--> amd_pstate_update_freq()
--> amd_pstate_update()
So these updates in amd_pstate_cpu_boost_update() seem redundant.
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
--
Thanks and Regards
gautham.
next prev parent reply other threads:[~2024-10-16 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 17:45 [PATCH 1/4] cpufreq/amd-pstate: Use nominal perf for limits when boost is disabled Mario Limonciello
2024-10-12 17:45 ` [PATCH 2/4] cpufreq/amd-pstate: Don't update CPPC request in amd_pstate_cpu_boost_update() Mario Limonciello
2024-10-16 4:42 ` Yuan, Perry
2024-10-16 9:50 ` Gautham R. Shenoy [this message]
2024-10-12 17:45 ` [PATCH 3/4] cpufreq/amd-pstate: Use amd_pstate_update_min_max_limit() for EPP limits Mario Limonciello
2024-10-16 4:38 ` Yuan, Perry
2024-10-16 10:14 ` Gautham R. Shenoy
2024-10-12 17:45 ` [PATCH 4/4] cpufreq/amd-pstate: Drop needless EPP initialization Mario Limonciello
2024-10-15 9:07 ` Dhananjay Ugwekar
2024-10-16 4:33 ` Yuan, Perry
2024-10-16 10:33 ` Gautham R. Shenoy
2024-10-16 4:10 ` [PATCH 1/4] cpufreq/amd-pstate: Use nominal perf for limits when boost is disabled Gautham R. Shenoy
2024-10-16 4:45 ` Yuan, Perry
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=Zw+MUOYw+nMuQ9Nk@BLRRASHENOY1.amd.com \
--to=gautham.shenoy@amd.com \
--cc=Dhananjay.Ugwekar@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.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