mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, stable@vger.kernel.org,
	mario.limonciello@amd.com, 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 12:41:47 +0200	[thread overview]
Message-ID: <d7527ee9-fba1-49ad-9a71-6d955eeddc3e@web.de> (raw)
In-Reply-To: <2025070646-unopposed-nutrient-8e1c@gregkh>

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.

WARNING: multiple messages have this Message-ID

From: "Jörg-Volker Peetz" <jvpeetz@web.de>
To: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: Linux 6.15.5
Date: Mon, 7 Jul 2025 12:41:47 +0200	[thread overview]
Message-ID: <d7527ee9-fba1-49ad-9a71-6d955eeddc3e@web.de> (raw)
Message-ID: <20250707104147.EJ_M4LBZ3cVDn3fvuEkz_rc2i0f0ElUuYZtjriwGRr4@z> (raw)
In-Reply-To: <2025070646-unopposed-nutrient-8e1c@gregkh>

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.


  parent reply	other threads:[~2025-07-07 10:41 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 [this message]
2025-07-07 10:41   ` Jörg-Volker Peetz
2025-07-07 21:52   ` 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=d7527ee9-fba1-49ad-9a71-6d955eeddc3e@web.de \
    --to=jvpeetz@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=dhananjay.ugwekar@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=mario.limonciello@amd.com \
    --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®