From: Borislav Petkov <bp@alien8.de>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Tony Luck <tony.luck@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Subject: Re: [tip: x86/cpu] x86/cpu: Add new Raptor Lake CPU model number
Date: Tue, 23 Aug 2022 09:57:46 +0200 [thread overview]
Message-ID: <YwSIeutdDadRgFf5@zn.tnic> (raw)
In-Reply-To: <166121188787.401.17379235294060223774.tip-bot2@tip-bot2>
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@intel.com>
> AuthorDate: Mon, 22 Aug 2022 10:12:21 -07:00
> Committer: Dave Hansen <dave.hansen@linux.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
prev parent reply other threads:[~2022-08-23 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YwO49TDHnLcOyE+F@agluck-desk3.sc.intel.com>
2022-08-22 23:44 ` tip-bot2 for Tony Luck
2022-08-23 7:57 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YwSIeutdDadRgFf5@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®