linux-kernel - Re: [tip: x86/cpu] x86/cpu: Add new Raptor Lake CPU model number

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: <YwSIeutdDadRgFf5@zn.tnic>
Date:   Tue, 23 Aug 2022 09:57:46 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     linux-kernel@...r.kernel.org
Cc:     linux-tip-commits@...r.kernel.org, Tony Luck <tony.luck@...el.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org
Subject: Re: [tip: x86/cpu] x86/cpu: Add new Raptor Lake CPU model number

On Mon, Aug 22, 2022 at 11:44:47PM -0000, tip-bot2 for Tony Luck wrote:
> The following commit has been merged into the x86/cpu branch of tip:
> 
> Commit-ID:     81779270304dd556e1bb9e62561115714c15fa6a
> Gitweb:        https://git.kernel.org/tip/81779270304dd556e1bb9e62561115714c15fa6a
> Author:        Tony Luck <tony.luck@...el.com>
> AuthorDate:    Mon, 22 Aug 2022 10:12:21 -07:00
> Committer:     Dave Hansen <dave.hansen@...ux.intel.com>
> CommitterDate: Mon, 22 Aug 2022 16:35:53 -07:00
> 
> x86/cpu: Add new Raptor Lake CPU model number
> 
> Note1: Model 0xB7 already claimed the "no suffix" #define for a regular
> client part, so add (yet another) suffix "S" to distinguish this new
> part from the earlier one.
> 
> Note2: the RAPTORLAKE* and ALDERLAKE* processors are very similar from a
> software enabling point of view.  There are no known features that have
> model-specific enabling and also differ between the two.  In other words,
> every single place that list *one* or more RAPTORLAKE* or ALDERLAKE*
> processors should eventually list all of them.
> 
> Note3: This is being merged before there is an in-tree user.  Merging
> this provides an "anchor" so that the different folks can update their
> subsystems (like perf) in parallel to use this define and test it.

Yeah, then you should probably stick it in x86/urgent so that it goes to
Linus now.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette