Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Lars Wendler <wendler.lars@web.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux kernel regressions list <regressions@lists.linux.dev>,
	"Huang, Ray" <Ray.Huang@amd.com>,
	"Yuan, Perry" <Perry.Yuan@amd.com>,
	"Shenoy, Gautham Ranjal" <gautham.shenoy@amd.com>,
	"Du, Xiaojian" <Xiaojian.Du@amd.com>,
	"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: linux-6.6.y: Regression in amd-pstate cpufreq driver since 6.6.34
Date: Mon, 1 Jul 2024 16:53:20 -0500	[thread overview]
Message-ID: <18882bfe-4ca5-495c-ace5-b9bcab796ae5@amd.com> (raw)
In-Reply-To: <20240701181349.5e8e76b8@chagall.paradoxon.rec>

On 7/1/2024 11:13, Lars Wendler wrote:
> Hello Mario,
> 
> Am Mon, 1 Jul 2024 10:58:17 -0500
> schrieb Mario Limonciello <mario.limonciello@amd.com>:
> 
>>> I've tested both, 6.9.7 and 6.10-rc6 and they both don't have that
>>> issue. I can disable CPU boost with both kernel versions.
>>
>> Thanks for checking those.  That's good to hear it's only an issue in
>> the LTS series.
>>
>> It means we have the option to either drop that patch from LTS kernel
>> series or identify the other commit(s) that helped it.
>>
>> Can you see if adding this commit to 6.6.y helps you?
>>
>> https://git.kernel.org/superm1/c/8164f743326404fbe00a721a12efd86b2a8d74d2
> 
> that commit does not fix the regression.
> 

I think I might have found the issue.

With that commit backported on 6.6.y in amd_pstate_set_boost() the 
policy max frequency is nominal  *1000 [1].

However amd_get_nominal_freq() already returns nominal *1000 [2].

If you compare on 6.9 get_nominal_freq() doesn't return * 1000 [3].

So the patch only makes sense on 6.9 and later.

We should revert it in 6.6.y.



Greg,


Can you please revert 8f893e52b9e0 ("cpufreq: amd-pstate: Fix the 
inconsistency in max frequency units") in 6.6.y?


[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/cpufreq/amd-pstate.c?h=linux-6.6.y#n678
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/cpufreq/amd-pstate.c?h=linux-6.6.y#n637
[3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/cpufreq/amd-pstate.c?h=linux-6.9.y#n703

  reply	other threads:[~2024-07-01 21:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240701112944.14de816f@chagall.paradoxon.rec>
     [not found] ` <SJ2PR12MB8690E3E2477CA9F558849835ECD32@SJ2PR12MB8690.namprd12.prod.outlook.com>
2024-07-01 15:07   ` FW: linux-6.6.y: Regression in amd-pstate cpufreq driver since 6.6.34 Mario Limonciello
2024-07-01 15:45     ` Lars Wendler
2024-07-01 15:58       ` Mario Limonciello
2024-07-01 16:13         ` Lars Wendler
2024-07-01 21:53           ` Mario Limonciello [this message]
2024-07-02  9:15             ` Greg Kroah-Hartman
2024-07-02  9:23               ` Greg Kroah-Hartman
2024-07-02 13:20                 ` 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=18882bfe-4ca5-495c-ace5-b9bcab796ae5@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Li.Meng@amd.com \
    --cc=Perry.Yuan@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=wendler.lars@web.de \
    /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