linux-kernel - Re: [PATCH 0/2] amd-pstate: Make amd-pstate the default driver on server platforms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d5d8783d-472d-4266-a0cd-e9eb7ba3cbac@amd.com>
Date: Mon, 21 Oct 2024 08:05:17 -0500
From: Mario Limonciello <mario.limonciello@....com>
To: "Gautham R. Shenoy" <gautham.shenoy@....com>,
 Perry Yuan <perry.yuan@....com>, Huang Rui <ray.huang@....com>,
 Dhananjay Ugwekar <Dhananjay.Ugwekar@....com>,
 Swapnil Sapkal <swapnil.sapkal@....com>,
 "Rafael J . Wysocki" <rafael@...nel.org>,
 Viresh Kumar <viresh.kumar@...aro.org>
Cc: linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] amd-pstate: Make amd-pstate the default driver on
 server platforms

On 10/21/2024 05:18, Gautham R. Shenoy wrote:
> Hello,
> 
> This patchset contains two patches to
> 
> * Prevent frequency throttling on power-limited systems with
>    amd-pstate active mode with performance governor.
> 
> * Make amd_pstate default on EPYC Family 1A+. Based on tests, the
>    amd-pstate driver performs well enough on EPYC.
> 
> These patches are based on the "linux-next" branch of
> https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
> 
> Gautham R. Shenoy (1):
>    amd-pstate: Set min_perf to nominal_perf for active mode performance
>      gov
> 
> Swapnil Sapkal (1):
>    amd-pstate: Switch to amd-pstate by default on some Server platforms
> 
>   drivers/cpufreq/amd-pstate.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 

Reviewed-by: Mario Limonciello <mario.limonciello@....com>

I'll queue this up for 6.13.

There were previously two differences for server and non-server:
  * amd-pstate not enabled by default
  * amd-pstate cpufreq policy starting in performance mode vs power-save?

This series adjusts the first for at least the newer parts, but I would 
like to ask does it make sense to also evaluating changing the default 
policy to powersave as a follow up, or should this policy delta remain?