From: Mario Limonciello <mario.limonciello@amd.com>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
gautham.shenoy@amd.com, dhananjay.ugwekar@amd.com,
ray.huang@amd.com, perry.yuan@amd.com, rafael@kernel.org,
viresh.kumar@linaro.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 6.15.5
Date: Mon, 7 Jul 2025 17:52:30 -0400 [thread overview]
Message-ID: <f8446083-815e-41e9-a1e8-f8d5c409dc36@amd.com> (raw)
In-Reply-To: <d7527ee9-fba1-49ad-9a71-6d955eeddc3e@web.de>
On 7/7/2025 6:41 AM, Jörg-Volker Peetz wrote:
> Hi,
>
> upgrading from linux kernel 6.14.9 to 6.15.2 and also now with 6.15.5 I
> noticed that on my system with cpufreq scaling driver amd-pstate the
> frequencies cpuinfo_min_freq and cpuinfo_max_freq increased, the min
> from 400 to 422.334 MHz, the max from 4,673 to 4,673.823 MHz. The CPU is
> an AMD Ryzen 7 5700G.
> This in turn increases other values (scaling_min_freq, scaling_max_freq,
> amd_pstate_lowest_nonlinear_freq, etc.).
>
> Bisecting this leads to
>
> commit a9b9b4c2a4cdd00428d14914e3c18be3856aba71
> From: Mario Limonciello <mario.limonciello@amd.com>
> Date: Thu, 23 Jan 2025 16:16:01 -0600
> Subject: [PATCH] cpufreq/amd-pstate: Drop min and max cached frequencies
>
> Did you notice the increase at AMD? Is it intended?
>
> Thanks,
> Jörg.
Yes; this was noticed back when it was created too. It's intended.
prev parent reply other threads:[~2025-07-07 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 9:13 Greg Kroah-Hartman
2025-07-06 9:13 ` Greg Kroah-Hartman
2025-07-06 16:47 ` Peter Jung
2025-07-07 5:55 ` Greg Kroah-Hartman
2025-07-07 10:41 ` Jörg-Volker Peetz
2025-07-07 10:41 ` Jörg-Volker Peetz
2025-07-07 21:52 ` Mario Limonciello [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=f8446083-815e-41e9-a1e8-f8d5c409dc36@amd.com \
--to=mario.limonciello@amd.com \
--cc=akpm@linux-foundation.org \
--cc=dhananjay.ugwekar@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=jvpeetz@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=perry.yuan@amd.com \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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®