[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f50abf9-e11a-4630-9970-f894c9caee52@amd.com>
Date: Thu, 5 Sep 2024 10:11:50 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: "Jones, Morgan" <Morgan.Jones@...sat.com>
Cc: "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Arcari <darcari@...hat.com>,
Dhananjay Ugwekar <Dhananjay.Ugwekar@....com>,
"rafael@...nel.org" <rafael@...nel.org>,
"viresh.kumar@...aro.org" <viresh.kumar@...aro.org>,
"gautham.shenoy@....com" <gautham.shenoy@....com>,
"perry.yuan@....com" <perry.yuan@....com>,
"skhan@...uxfoundation.org" <skhan@...uxfoundation.org>,
"li.meng@....com" <li.meng@....com>, "ray.huang@....com" <ray.huang@....com>
Subject: Re: [EXTERNAL] Re: [PATCH v2 2/2] cpufreq/amd-pstate: Fix the
scaling_max_freq setting on shared memory CPPC systems
Hi Morgan,
Please apply these 3 commits:
commit 12753d71e8c5 ("ACPI: CPPC: Add helper to get the highest
performance value")
commit ed429c686b79 ("cpufreq: amd-pstate: Enable amd-pstate preferred
core support")
commit 3d291fe47fe1 ("cpufreq: amd-pstate: fix the highest frequency
issue which limits performance")
The first two should help your system, the third will prevent
introducing a regression on a different one.
Assuming that works we should ask @stable to pull all 3 in to fix this
regression.
Thanks,
On 9/4/2024 08:57, Mario Limonciello wrote:
> Morgan,
>
> I was referring specfiically to the version that landed in Linus' tree:
> https://git.kernel.org/torvalds/c/8164f7433264
>
> But yeah it's effectively the same thing. In any case, it's not the
> solution.
>
> We had some internal discussion and suspect this is due to missing
> prefcore patches in 6.6 as that feature landed in 6.9. We'll try to
> reproduce this on a Rome system and come back with our findings and
> suggestions what to do.
>
> Thanks,
>
Powered by blists - more mailing lists