linux-kernel - Re: [PATCH] cpufreq: acpi: Don't enable boost on policy exit

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: <20250417050226.c6kdp2s5du3y3a3j@vireshk-i7>
Date: Thu, 17 Apr 2025 10:32:26 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Nicholas Chin <nic.c3.14@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	rafael.j.wysocki@...el.com, rafael@...nel.org,
	vincent.guittot@...aro.org, zhenglifeng1@...wei.com
Subject: Re: [PATCH] cpufreq: acpi: Don't enable boost on policy exit

On 16-04-25, 19:54, Nicholas Chin wrote:
> Unfortunately the issue I reported still seems to be present after
> applying this patch. Upon resuming from suspend, the system is still
> entering boost states descpite the boost flag being set to 0.

Okay, so this is what we know so far:

- Force synchronizing (disabling here) boost state at resume was
  making this work earlier.

- Setting the boost flag to "enabled" state during resume works as
  well, as that makes the cpufreq core disable the boost frequencies
  again.

- This patch (though doing the correct thing) doesn't work. This is
  one of the known places where boost was getting enabled before going
  to suspend though.

- This means that some other part of kernel (or hardware ?) is
  enabling the boost frequencies at suspend (or early resume), which
  the kernel was disabling earlier and not anymore.

Rafael, any suggestions ?

-- 
viresh