mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Jones, Morgan" <Morgan.Jones@viasat.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Arcari <darcari@redhat.com>,
	Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"gautham.shenoy@amd.com" <gautham.shenoy@amd.com>,
	"perry.yuan@amd.com" <perry.yuan@amd.com>,
	"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
	"li.meng@amd.com" <li.meng@amd.com>,
	"ray.huang@amd.com" <ray.huang@amd.com>
Subject: Re: [EXTERNAL] Re: [PATCH v2 2/2] cpufreq/amd-pstate: Fix the scaling_max_freq setting on shared memory CPPC systems
Date: Thu, 5 Sep 2024 10:11:50 -0500	[thread overview]
Message-ID: <7f50abf9-e11a-4630-9970-f894c9caee52@amd.com> (raw)
In-Reply-To: <d6808d8e-acaf-46ac-812a-0a3e1df75b09@amd.com>

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,
> 


  reply	other threads:[~2024-09-05 15:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  8:14 [PATCH v2 0/2] AMD Pstate driver fixes Dhananjay Ugwekar
2024-07-02  8:14 ` [PATCH v2 1/2] cpufreq/amd-pstate-ut: Convert nominal_freq to khz during comparisons Dhananjay Ugwekar
2024-07-02  8:14 ` [PATCH v2 2/2] cpufreq/amd-pstate: Fix the scaling_max_freq setting on shared memory CPPC systems Dhananjay Ugwekar
2024-07-02 17:49   ` Mario Limonciello
2024-09-03 17:51     ` Jones, Morgan
2024-09-03 17:54       ` Mario Limonciello
2024-09-03 20:07         ` [EXTERNAL] " Jones, Morgan
2024-09-03 20:09           ` Mario Limonciello
2024-09-03 20:51             ` Mario Limonciello
2024-09-03 20:52               ` Jones, Morgan
2024-09-03 22:21               ` Jones, Morgan
2024-09-03 22:24               ` Jones, Morgan
2024-09-04 13:57                 ` Mario Limonciello
2024-09-05 15:11                   ` Mario Limonciello [this message]
2024-09-05 21:09                     ` Jones, Morgan
2024-09-05 21:14                       ` linux-6.6.y regression on amd-pstate Mario Limonciello
2024-09-08 14:05                         ` Greg Kroah-Hartman
2024-09-08 14:12                           ` Christian Heusel
2024-09-08 14:29                             ` Greg Kroah-Hartman
2025-07-31 20:44                               ` [EXTERNAL] " Jones, Morgan
2025-08-01 12:32                                 ` Mario Limonciello
2024-09-03 20:52             ` [EXTERNAL] Re: [PATCH v2 2/2] cpufreq/amd-pstate: Fix the scaling_max_freq setting on shared memory CPPC systems Jones, Morgan
2024-07-03  5:46   ` Gautham R.Shenoy
2024-07-02  8:24 ` [PATCH v2 0/2] AMD Pstate driver fixes Dhananjay Ugwekar
2024-07-02 17:54   ` Mario Limonciello

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=7f50abf9-e11a-4630-9970-f894c9caee52@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Dhananjay.Ugwekar@amd.com \
    --cc=Morgan.Jones@viasat.com \
    --cc=darcari@redhat.com \
    --cc=gautham.shenoy@amd.com \
    --cc=li.meng@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®