linux-kernel - Re: [PATCH] cpufreq/amd-pstate: Add comment explaining nominal

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] [day] [month] [year] [list]

Message-ID: <rdym4zzkiokzvmlj6qmxzomgyazggzfbj4euwlbp2nq7yhop6u@3qg4yo6zamkl>
Date: Mon, 19 Jan 2026 11:18:49 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Juan Martinez <juan.martinez@....com>
Cc: Ray.Huang@....com, gautham.shenoy@....com, Mario.Limonciello@....com, 
	rafael@...nel.org, Perry.Yuan@....com, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, stable@...r.kernel.org, Kaushik.ReddyS@....com
Subject: Re: [PATCH] cpufreq/amd-pstate: Add comment explaining nominal_perf
 usage for performance policy

On 16-01-26, 15:45, Juan Martinez wrote:
> Add comment explaining why nominal_perf is used for MinPerf when the
> CPU frequency policy is set to CPUFREQ_POLICY_PERFORMANCE, rather than
> using highest_perf or lowest_nonlinear_perf.
> 
> Signed-off-by: Juan Martinez <juan.martinez@....com>
> ---
>  drivers/cpufreq/amd-pstate.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index c45bc98721d2..88b26f36937b5 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -636,6 +636,19 @@ static void amd_pstate_update_min_max_limit(struct cpufreq_policy *policy)
>  	WRITE_ONCE(cpudata->max_limit_freq, policy->max);
>  
>  	if (cpudata->policy == CPUFREQ_POLICY_PERFORMANCE) {
> +		/*
> +		 * For performance policy, set MinPerf to nominal_perf rather than
> +		 * highest_perf or lowest_nonlinear_perf.
> +		 *
> +		 * Per commit 0c411b39e4f4c, using highest_perf was observed
> +		 * to cause frequency throttling on power-limited platforms, leading to
> +		 * performance regressions. Using lowest_nonlinear_perf would limit
> +		 * performance too much for HPC workloads requiring high frequency
> +		 * operation and minimal wakeup latency from idle states.
> +		 *
> +		 * nominal_perf therefore provides a balance by avoiding throttling
> +		 * while still maintaining enough performance for HPC workloads.
> +		 */
>  		perf.min_limit_perf = min(perf.nominal_perf, perf.max_limit_perf);
>  		WRITE_ONCE(cpudata->min_limit_freq, min(cpudata->nominal_freq, cpudata->max_limit_freq));
>  	} else {

Applied. Thanks.

-- 
viresh