linux-kernel - Re: [PATCH v2] arm64: Utilize for_each_cpu

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: <174013080894.2262863.4824734189364820879.b4-ty@arm.com>
Date: Fri, 21 Feb 2025 09:40:24 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	sudeep.holla@....com,
	will@...nel.org,
	sfr@...b.auug.org.au,
	Beata Michalska <beata.michalska@....com>
Cc: ionela.voinescu@....com,
	yury.norov@...il.com,
	linux-next@...r.kernel.org,
	sumitg@...dia.com,
	yang@...amperecomputing.com,
	vanshikonda@...amperecomputing.com,
	lihuisong@...wei.com,
	zhanjie9@...ilicon.com,
	ptsm@...ux.microsoft.com
Subject: Re: [PATCH v2] arm64: Utilize for_each_cpu_wrap for reference lookup

On Thu, 20 Feb 2025 09:10:15 +0000, Beata Michalska wrote:
> While searching for a reference CPU within a given policy,
> arch_freq_get_on_cpu relies on cpumask_next_wrap to iterate over
> all available CPUs and to ensure each is verified only once.
> Recent changes to cpumask_next_wrap will handle the latter no more,
> so switching to for_each_cpu_wrap, which  preserves expected behavior
> while ensuring compatibility with the updates.
> Not to mention that when iterating over each CPU, using a dedicated
> iterator is preferable to an open-coded loop.
> 
> [...]

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

[1/1] arm64: Utilize for_each_cpu_wrap for reference lookup
      https://git.kernel.org/arm64/c/20711efa91e8

-- 
Catalin