linux-kernel - [PATCH v1 0/4] cpufreq: Fixes and cleanups related to CPUFREQ

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

Message-ID: <8605612.T7Z3S40VBb@rafael.j.wysocki>
Date: Thu, 25 Sep 2025 17:42:16 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: Shawn Guo <shawnguo@...nel.org>, Qais Yousef <qyousef@...alina.io>,
 LKML <linux-kernel@...r.kernel.org>, Viresh Kumar <viresh.kumar@...aro.org>,
 Prashanth Prakash <pprakash@...eaurora.org>,
 Pierre Gondois <pierre.gondois@....com>,
 Mario Limonciello <mario.limonciello@....com>,
 Linux ACPI <linux-acpi@...r.kernel.org>
Subject: [PATCH v1 0/4] cpufreq: Fixes and cleanups related to CPUFREQ_ETERNAL

Hi All,

The first patch in this series is meant to address the failure discussed in

https://lore.kernel.org/linux-pm/20250922125929.453444-1-shawnguo2@yeah.net/

but in a different way than proposed by Shawn.

The second one is a CPPC cpufreq driver fix preventing it from using an
overly large transition delay in the cases when that delay cannot be
obtained from the platform firmware.

Patch [3/4] makes CPPC use a specific symbol instead of CPUFREQ_ETERNAL for
signaling error conditions while attempting to retrieve a transition latency
value from the platform firmware.

The last patch removes CPUFREQ_ETERNAL (which has no users any more) from
cpufreq, including all references to it in cpufreq documentation.

Thanks!