linux-kernel - Re: [PATCH v1 19/26] x86/cacheinfo: Use scanned CPUID(0x4)

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: <aBnEBbDATdE2LTGU@gmail.com>
Date: Tue, 6 May 2025 10:10:45 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "Ahmed S. Darwish" <darwi@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	John Ogness <john.ogness@...utronix.de>, x86@...nel.org,
	x86-cpuid@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 19/26] x86/cacheinfo: Use scanned CPUID(0x4)


* Ahmed S. Darwish <darwi@...utronix.de> wrote:

> Refactor the Intel CPUID(0x4) cacheinfo logic to use scanned CPUID access
> instead of issuing direct CPUID queries.
> 
> Since scanned CPUID access requires a cpuinfo_x86 reference, propagate it
> down from <linux/cacheinfo.h>'s populate_cache_leaves() to all the
> relevant functions.

Could you please split this patch into two parts, first one does the 
mechanical propagation of the cpuinfo_x86 pointer down the function, 
the second one does functional changes?

Thanks,

	Ingo