From: "Gautham R. Shenoy" <gautham.shenoy@amd.com>
To: Perry Yuan <perry.yuan@amd.com>
Cc: rafael.j.wysocki@intel.com, Mario.Limonciello@amd.com,
viresh.kumar@linaro.org, Ray.Huang@amd.com,
Borislav.Petkov@amd.com, Alexander.Deucher@amd.com,
Xinmei.Huang@amd.com, Xiaojian.Du@amd.com, Li.Meng@amd.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/6] cpufreq:amd-pstate: fix the nominal freq value set
Date: Thu, 8 Feb 2024 11:37:29 +0530 [thread overview]
Message-ID: <ZcRvoYZKdUEjBUHp@BLR-5CG11610CF.amd.com> (raw)
In-Reply-To: <ebbe3741501a31b1ffcea208393cdd8929df6455.1707363758.git.perry.yuan@amd.com>
On Thu, Feb 08, 2024 at 11:46:29AM +0800, Perry Yuan wrote:
> Address an untested error where the nominal_freq was returned in KHz
> instead of the correct MHz units, this oversight led to a wrong
> nominal_freq set and resued, it will cause the max frequency of core to
> be initialized with a wrong frequency value.
The _CPC object on my Zen2 EPYC server which has CPPC v3, I see :
0x00000190, //LowestFrequency
0x000007D0 //NominalFrequency
})
}
where 0x7D0 is 2000 Mhz. Thus the value returend by cppc_perf.nominal_freq is in Mhz.
In this patch, we are changing making amd_get_nominal_freq() return
2000 (Mhz) instead of 2000000 (Khz) as it was doing previously.
amd_get_min_freq(), amd_get_max_freq(),
amd_get_lowest_nonlinear_perf() -all these functions return the
frequency in Khz units.
These functions are used the initialize the value of
cpudata->max_freq, cpu_data->min_freq, .... all of which are in Khz
units.
In, amd_pstate_set_boost(), we have:
if (state)
policy->cpuinfo.max_freq = cpudata->max_freq; <---- In Khz
else
policy->cpuinfo.max_freq = cpudata->nominal_freq; <--- Now in Mhz
Since policy->cpuinfo.max_freq is expected to be in Khz, isn't this
patch introducing an error ? Or perhaps this patch series is based on
another patchset ?
--
Thanks and Regards
gautham.
>
> Cc: stable@vger.kernel.org
> Fixes: ec437d71db7 ("cpufreq: amd-pstate: Introduce a new AMD P-State driver to support future processors")
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> Signed-off-by: Perry Yuan <perry.yuan@amd.com>
> ---
> drivers/cpufreq/amd-pstate.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index 08e112444c27..ac7faa98a450 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -640,8 +640,7 @@ static int amd_get_nominal_freq(struct amd_cpudata *cpudata)
> if (ret)
> return ret;
>
> - /* Switch to khz */
> - return cppc_perf.nominal_freq * 1000;
> + return cppc_perf.nominal_freq;
> }
>
> static int amd_get_lowest_nonlinear_freq(struct amd_cpudata *cpudata)
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-02-08 6:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 3:46 [PATCH v6 0/6] AMD Pstate Fixes And Enhancements Perry Yuan
2024-02-08 3:46 ` [PATCH v6 1/6] ACPI: CPPC: enable AMD CPPC V2 support for family 17h processors Perry Yuan
2024-02-08 5:55 ` Gautham R. Shenoy
2024-03-05 12:25 ` Rafael J. Wysocki
2024-02-08 3:46 ` [PATCH v6 2/6] cpufreq:amd-pstate: fix the nominal freq value set Perry Yuan
2024-02-08 6:07 ` Gautham R. Shenoy [this message]
2024-03-11 9:58 ` Ugwekar, Dhananjay
2024-02-08 3:46 ` [PATCH v6 3/6] cpufreq:amd-pstate: initialize nominal_freq of each cpudata Perry Yuan
2024-02-08 6:34 ` Gautham R. Shenoy
2024-02-08 3:46 ` [PATCH v6 4/6] cpufreq:amd-pstate: get pstate transition delay and latency value from ACPI tables Perry Yuan
2024-02-08 3:46 ` [PATCH v6 5/6] cppc_acpi: print error message if CPPC is unsupported Perry Yuan
2024-02-08 6:46 ` Gautham R. Shenoy
2024-02-08 3:46 ` [PATCH v6 6/6] cpufreq:amd-pstate: add quirk for the pstate CPPC capabilities missing Perry Yuan
2024-02-08 9:53 ` Gautham R. Shenoy
2024-02-08 10:21 ` [PATCH v6 0/6] AMD Pstate Fixes And Enhancements Borislav Petkov
2024-02-08 23:09 ` Deucher, Alexander
2024-02-09 15:51 ` Borislav Petkov
2024-02-09 17:33 ` Deucher, Alexander
2024-02-09 17:41 ` Borislav Petkov
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=ZcRvoYZKdUEjBUHp@BLR-5CG11610CF.amd.com \
--to=gautham.shenoy@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Borislav.Petkov@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Ray.Huang@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=Xinmei.Huang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=perry.yuan@amd.com \
--cc=rafael.j.wysocki@intel.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
all inboxes | Powered by JetHome®