linux-kernel - Re: [PATCH] x86/cpu: Add new Alderlake and Raptorlake CPU model numbers

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]

Date:   Tue, 19 Apr 2022 10:56:03 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     "Luck, Tony" <tony.luck@...el.com>
Cc:     Borislav Petkov <bp@...en8.de>, "x86@...nel.org" <x86@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/cpu: Add new Alderlake and Raptorlake CPU model
 numbers

On Mon, Apr 11, 2022 at 04:37:03PM -0700, Luck, Tony wrote:
> Intel is subdividing the mobile segment with additional models
> with the same codename. Using the Intel "N" and "P" suffices
> for these will be less confusing than trying to map to some
> different naming convention.
> 
> Signed-off-by: Tony Luck <tony.luck@...el.com>
> ---
> 
> I think the earlier patch for Alderlake "N" got stuck in limbo
> trying to resolve whether we should add the "_N" suffix to our list
> of acceptable CPU model #define names. Now we have another one "_P".
> 
> Can we just take these, and move on?

Yeah, I suppose so.

Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>

Let's hope our marketing team will stick with these names for a little
while atleast :/