linux-kernel - RE: [PATCH 01/74] x86/cpu/vfm: Add/initialize x86_vfm field to struct cpuinfo

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: <SJ1PR11MB6083F100B4D957EC472AFF19FC082@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Tue, 16 Apr 2024 21:45:49 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: Thomas Gleixner <tglx@...utronix.de>, "x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 01/74] x86/cpu/vfm: Add/initialize x86_vfm field to struct
 cpuinfo_x86

> Alternatively, we can take the arch/x86 parts and once 6.10 releases,
> the other maintainers will have them in tree and thus not need the
> cross-tree merges.

I did a bit of this. I moved all the arch/x86 patches up to immediately follow
the three prep patches. So you can pick through parts 0004..0039 and apply
any that look good to you (there is no ordering requirement among these).
Bounce anything that needs extra work back to me.

> Or you can post the whole series and we can take it all through tip once
> the other maintainers ack the respective patch for their area. Which
> sounds like the simplest solution to me...

Also a bit of this. Parts 0040..0072 are posted to whomever get_maintainer.pl
said might be interested. So may see some reviews coming in for these.

Parts 0073..0074 are the cleanup to delete the old macros. They can only
be applied after everything else has been merged.

-Tony