From: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
To: Mario Limonciello <superm1@kernel.org>,
"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
Perry Yuan <perry.yuan@amd.com>
Cc: "open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:CPU FREQUENCY SCALING FRAMEWORK"
<linux-pm@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>,
Sebastian <sobrus@gmail.com>
Subject: Re: [PATCH] cpufreq/amd-pstate: Fix prefcore rankings
Date: Fri, 3 Jan 2025 10:21:20 +0530 [thread overview]
Message-ID: <4a0386d0-24f1-4b13-9111-6e4ea34083cd@amd.com> (raw)
In-Reply-To: <20250102141204.3413202-1-superm1@kernel.org>
On 1/2/2025 7:42 PM, Mario Limonciello wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> commit 50a062a76200 ("cpufreq/amd-pstate: Store the boost numerator as
> highest perf again") updated the value stored for highest perf to no longer
> store the highest perf value but instead the boost numerator.
>
> This is a fixed value for systems with preferred cores and not appropriate
> for use ITMT rankings. Update the value used for ITMT rankings to be the
> preferred core ranking.
Looks good to me,
Reviewed-by: Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>
Thanks,
Dhananjay
>
> Reported-and-tested-by: Sebastian <sobrus@gmail.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=219640
> Fixes: 50a062a76200 ("cpufreq/amd-pstate: Store the boost numerator as highest perf again")
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/cpufreq/amd-pstate.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index 66e5dfc711c0c..f6d04eb40af94 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -802,7 +802,7 @@ static void amd_pstate_init_prefcore(struct amd_cpudata *cpudata)
> * sched_set_itmt_support(true) has been called and it is valid to
> * update them at any time after it has been called.
> */
> - sched_set_itmt_core_prio((int)READ_ONCE(cpudata->highest_perf), cpudata->cpu);
> + sched_set_itmt_core_prio((int)READ_ONCE(cpudata->prefcore_ranking), cpudata->cpu);
>
> schedule_work(&sched_prefcore_work);
> }
prev parent reply other threads:[~2025-01-03 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 14:12 Mario Limonciello
2025-01-03 4:51 ` Dhananjay Ugwekar [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=4a0386d0-24f1-4b13-9111-6e4ea34083cd@amd.com \
--to=dhananjay.ugwekar@amd.com \
--cc=gautham.shenoy@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=sobrus@gmail.com \
--cc=superm1@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
all inboxes | Powered by JetHome®