From: "Luck, Tony" <tony.luck@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Borislav Petkov <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] x86/cpu: Add a third Alderlake CPU model number
Date: Wed, 30 Mar 2022 19:57:09 +0000 [thread overview]
Message-ID: <29d602962d6542bd90e877c104afcc7f@intel.com> (raw)
In-Reply-To: <20220330134325.GM8939@worktop.programming.kicks-ass.net>
>> +#define INTEL_FAM6_ALDERLAKE_N 0xBE
>
> This is missing the /* Gracemont */ comment. That is, according to
> Google, Alder Lake N is an E core only SKU.
I can neither confirm nor deny that information.
> So alternatively, we can
> call it: INTEL_FAM6_ATOM_GRACEMONT ....
>
> /me runs like heck :-)
And so you should :-) I think that will just cause a different level
of confusion.
-Tony
next prev parent reply other threads:[~2022-03-30 19:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 21:56 [PATCH] x86/cpu: Add a third Alderlake CPU model number Tony Luck
2022-03-30 13:43 ` Peter Zijlstra
2022-03-30 19:57 ` Luck, Tony [this message]
2022-04-11 23:37 ` [PATCH] x86/cpu: Add new Alderlake and Raptorlake CPU model numbers Luck, Tony
2022-04-19 8:56 ` Peter Zijlstra
2022-04-19 10:01 ` Borislav Petkov
2022-04-19 10:16 ` [tip: x86/urgent] " tip-bot2 for Tony Luck
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=29d602962d6542bd90e877c104afcc7f@intel.com \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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