Re: [PATCH] cpufreq: Don't track pressure if policy->max equals top of freq_table

[Giovanni Gherdovich]

On Fri Oct 9, 2026 11:40, Christian Loehle wrote:
> On 10/9/26 09:29, Giovanni Gherdovich wrote:
> > The acpi-cpufreq driver stores non-boost frequencies in
> > policy->freq_table, but policy->cpuinfo.max_freq contains the max
> > boost frequency.
> >
> > policy->max is constrained to be, at most, the largest value in
> > freq_table. This means that under nominal conditions, policy->max is
> > substantially lower than policy->cpuinfo.max_freq, resulting in large
> > values of cpufreq_pressure, on all CPUs, for no reason.
>
>
> I'm assuming this isn't on top of
> f341dc4d934a ("cpufreq: intel_pstate: Fix max_freq fallback in cpufreq_update_pressure()")
> Care to retry?

Ah! Yes that fixes it.

Pressure is zero on all CPUs under nominal conditions with acpi-cpufreq;
not tracked, as the commit makes it conditional to the driver implementing
.scale_freq.

Thanks Christian for pointing that out.


Giovanni