From: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, viresh.kumar@linaro.org,
gautham.shenoy@amd.com, perry.yuan@amd.com,
skhan@linuxfoundation.org, li.meng@amd.com, ray.huang@amd.com
Subject: Re: [PATCH 1/2] cpufreq/amd-pstate-ut: Handle the inconsistency
Date: Wed, 26 Jun 2024 13:26:09 +0530 [thread overview]
Message-ID: <e1132f04-9569-4f64-9b6a-96cd810ef5b8@amd.com> (raw)
In-Reply-To: <e9811d4e-60bb-49ea-80da-5d4597ef8705@amd.com>
Hello Mario,
On 6/25/2024 8:41 PM, Mario Limonciello wrote:
> On 6/25/2024 08:51, Dhananjay Ugwekar wrote:
>> Minor modification, the commit subject is supposed to be
>> "cpufreq/amd-pstate-ut: Handle the inconsistency between nominal_freq and other *_freq units"
>>
>> The second half disappeared due to the word wrapping I guess.
>
> I had some other feedback on the series, so when you submit a v2 can you try to fix the title on the first patch?
Yup, will do!
Thanks,
Dhananjay
>
>>
>> Regards,
>> Dhananjay
>>
>> On 6/25/2024 7:11 PM, Dhananjay Ugwekar wrote:
>>> cpudata->nominal_freq being in MHz whereas other frequencies being in
>>> KHz breaks the amd-pstate-ut frequency sanity check. This fixes it.
>>>
>>> Fixes: 14eb1c96e3a3 ("cpufreq: amd-pstate: Add test module for amd-pstate driver")
>>> Signed-off-by: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
>>> ---
>>> drivers/cpufreq/amd-pstate-ut.c | 12 +++++++-----
>>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/cpufreq/amd-pstate-ut.c b/drivers/cpufreq/amd-pstate-ut.c
>>> index fc275d41d51e..66b73c308ce6 100644
>>> --- a/drivers/cpufreq/amd-pstate-ut.c
>>> +++ b/drivers/cpufreq/amd-pstate-ut.c
>>> @@ -202,6 +202,7 @@ static void amd_pstate_ut_check_freq(u32 index)
>>> int cpu = 0;
>>> struct cpufreq_policy *policy = NULL;
>>> struct amd_cpudata *cpudata = NULL;
>>> + u32 nominal_freq_khz;
>>> for_each_possible_cpu(cpu) {
>>> policy = cpufreq_cpu_get(cpu);
>>> @@ -209,13 +210,14 @@ static void amd_pstate_ut_check_freq(u32 index)
>>> break;
>>> cpudata = policy->driver_data;
>>> - if (!((cpudata->max_freq >= cpudata->nominal_freq) &&
>>> - (cpudata->nominal_freq > cpudata->lowest_nonlinear_freq) &&
>>> + nominal_freq_khz = cpudata->nominal_freq*1000;
>>> + if (!((cpudata->max_freq >= nominal_freq_khz) &&
>>> + (nominal_freq_khz > cpudata->lowest_nonlinear_freq) &&
>>> (cpudata->lowest_nonlinear_freq > cpudata->min_freq) &&
>>> (cpudata->min_freq > 0))) {
>>> amd_pstate_ut_cases[index].result = AMD_PSTATE_UT_RESULT_FAIL;
>>> pr_err("%s cpu%d max=%d >= nominal=%d > lowest_nonlinear=%d > min=%d > 0, the formula is incorrect!\n",
>>> - __func__, cpu, cpudata->max_freq, cpudata->nominal_freq,
>>> + __func__, cpu, cpudata->max_freq, nominal_freq_khz,
>>> cpudata->lowest_nonlinear_freq, cpudata->min_freq);
>>> goto skip_test;
>>> }
>>> @@ -229,13 +231,13 @@ static void amd_pstate_ut_check_freq(u32 index)
>>> if (cpudata->boost_supported) {
>>> if ((policy->max == cpudata->max_freq) ||
>>> - (policy->max == cpudata->nominal_freq))
>>> + (policy->max == nominal_freq_khz))
>>> amd_pstate_ut_cases[index].result = AMD_PSTATE_UT_RESULT_PASS;
>>> else {
>>> amd_pstate_ut_cases[index].result = AMD_PSTATE_UT_RESULT_FAIL;
>>> pr_err("%s cpu%d policy_max=%d should be equal cpu_max=%d or cpu_nominal=%d !\n",
>>> __func__, cpu, policy->max, cpudata->max_freq,
>>> - cpudata->nominal_freq);
>>> + nominal_freq_khz);
>>> goto skip_test;
>>> }
>>> } else {
>
next prev parent reply other threads:[~2024-06-26 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:41 [PATCH 0/2] AMD Pstate driver fixes Dhananjay Ugwekar
2024-06-25 13:41 ` [PATCH 1/2] cpufreq/amd-pstate-ut: Handle the inconsistency Dhananjay Ugwekar
2024-06-25 13:51 ` Dhananjay Ugwekar
2024-06-25 15:11 ` Mario Limonciello
2024-06-26 7:56 ` Dhananjay Ugwekar [this message]
2024-06-26 1:49 ` Meng, Li (Jassmine)
2024-06-26 5:22 ` Gautham R.Shenoy
2024-06-26 6:45 ` Dhananjay Ugwekar
2024-06-25 15:05 ` Mario Limonciello
2024-06-26 8:02 ` Dhananjay Ugwekar
2024-06-25 13:41 ` [PATCH 2/2] cpufreq/amd-pstate: Fix the scaling_min/max_freq setting on shared memory CPPC systems Dhananjay Ugwekar
2024-06-25 15:09 ` Mario Limonciello
2024-06-26 8:10 ` Dhananjay Ugwekar
2024-06-26 5:24 ` Gautham R.Shenoy
2024-06-26 7:57 ` Dhananjay Ugwekar
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=e1132f04-9569-4f64-9b6a-96cd810ef5b8@amd.com \
--to=dhananjay.ugwekar@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=li.meng@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=skhan@linuxfoundation.org \
--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