Linux Power Management development
 help / color / mirror / Atom feed
From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Dhruva Gole <d-gole@ti.com>, Lukasz Luba <lukasz.luba@arm.com>,
	Qais Yousef <qyousef@layalina.io>, Ingo Molnar <mingo@kernel.org>,
	zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH v1] cpufreq: Make cpufreq_update_pressure() fall back to cpuinfo.max_freq
Date: Wed, 8 Jul 2026 12:09:18 +0800	[thread overview]
Message-ID: <4430befd-2d2c-422f-98b5-5947bb633937@oss.qualcomm.com> (raw)
In-Reply-To: <xdiwzy332y7inq4nnb2ht3xklm7acye4u3b3ar4psbak6rax3l@zsa6icmznqfx>

On 7/8/2026 11:44 AM, Viresh Kumar wrote:
> On 07-07-26, 19:25, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>
>> If arch_scale_freq_ref() is not defined for a given arch (like x86, for
>> example), cpufreq_update_pressure() will always set cpufreq_pressure to
>> zero for all CPUs in the system, which is generally problematic on
>> systems with asymmetric capacity [1].
>>
>> However, in the absence of arch_scale_freq_ref(), it is reasonable
>> to assume that cpuinfo.max_freq is the maximum sustainable frequency
>> for the given cpufreq policy.  Moreover, there are cases in which
>> arch_scale_freq_ref() would need to be defined to return essentially
>> the cpuinfo.max_freq value anyway (for example, intel_pstate on
>> hybrid platforms).
>>
>> For the above reasons, update cpufreq_update_pressure() to fall back to
>> using cpuinfo.max_freq as the reference frequency if zero is returned by
>> arch_scale_freq_ref().
>>
>> Fixes: 75d659317bb1 ("cpufreq: Add a cpufreq pressure feedback for the scheduler")
>> Link: https://lore.kernel.org/lkml/CAKfTPtBuRLfYNnR4w--cFZYZy-R8gaPEgVwCcaMmbCcJ2H-muQ@mail.gmail.com/ [1]
>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> ---
>>   drivers/cpufreq/cpufreq.c |    3 +++
>>   1 file changed, 3 insertions(+)
>>
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -2590,6 +2590,9 @@ static void cpufreq_update_pressure(stru
>>   
>>   	cpu = cpumask_first(policy->related_cpus);
>>   	max_freq = arch_scale_freq_ref(cpu);
>> +	if (!max_freq)
>> +		max_freq = policy->cpuinfo.max_freq;
>> +
>>   	capped_freq = policy->max;
>>   
>>   	/*
> 
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> 

Reviewed-by: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>

-- 
Thx and BRs,
Zhongqiu Han

  reply	other threads:[~2026-07-08  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 17:25 [PATCH v1] cpufreq: Make cpufreq_update_pressure() fall back to cpuinfo.max_freq Rafael J. Wysocki
2026-07-08  3:44 ` Viresh Kumar
2026-07-08  4:09   ` Zhongqiu Han [this message]
2026-07-08 17:13 ` Ricardo Neri
2026-07-09 13:00 ` Vincent Guittot

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=4430befd-2d2c-422f-98b5-5947bb633937@oss.qualcomm.com \
    --to=zhongqiu.han@oss.qualcomm.com \
    --cc=d-gole@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mingo@kernel.org \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=vincent.guittot@linaro.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