linux-kernel - Re: [PATCH] arch_topology: init capacity_freq

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: <173982791747.4020779.3793606958598624272.b4-ty@arm.com>
Date: Mon, 17 Feb 2025 21:32:18 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	sudeep.holla@....com,
	vincent.guittot@...aro.org,
	beata.michalska@....com,
	Ionela Voinescu <ionela.voinescu@....com>
Cc: Will Deacon <will@...nel.org>,
	rafael@...nel.org,
	viresh.kumar@...aro.org,
	dietmar.eggemann@....com,
	pierre.gondois@....com
Subject: Re: [PATCH] arch_topology: init capacity_freq_ref to 0

On Tue, 27 Aug 2024 16:48:18 +0100, Ionela Voinescu wrote:
> It's useful to have capacity_freq_ref initialized to 0 for users of
> arch_scale_freq_ref() to detect when capacity_freq_ref was not
> yet set.
> 
> The only scenario affected by this change in the init value is when a
> cpufreq driver is never loaded. As a result, the only setter of a
> cpu scale factor remains the call of topology_normalize_cpu_scale()
> from parse_dt_topology(). There we cannot use the value 0 of
> capacity_freq_ref so we have to compensate for its uninitialized state.
> 
> [...]

Applied to arm64 (for-next/amuv1-avg-freq), thanks!

[1/1] arch_topology: init capacity_freq_ref to 0
      https://git.kernel.org/arm64/c/004b500a9031

-- 
Catalin