From: Andrew Cooper <andrew.cooper3@citrix.com>
To: tony.luck@intel.com
Cc: dave.hansen@intel.com, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, x86@kernel.org
Subject: Re: [PATCH] x86/cpu: Add two Intel CPU model numbers
Date: Wed, 12 Feb 2025 01:39:16 +0000 [thread overview]
Message-ID: <c8545ed5-b822-43a0-a347-d077bccf9d6f@citrix.com> (raw)
In-Reply-To: <20240923173750.16874-1-tony.luck@intel.com>
> @@ -178,4 +180,7 @@ #define INTEL_FAM5_QUARK_X1000 0x09 /* Quark X1000 SoC */
> #define INTEL_QUARK_X1000 IFM(5, 0x09) /* Quark X1000 SoC */
>
> +/* Family 19 */ +#define INTEL_PANTHERCOVE_X IFM(19, 0x01) /* Diamond
> Rapids */
Is it intentional that this is not INTEL_DIAMONDRAPIDS_X like
Sappire/Emerald/Granite ?
I was going to submit a patch, but there are other inconsistencies too;
the Cores and Atoms are mostly the opposite ways around.
Atoms uses the microarchitecture codename with SoC name in the comment.
Cores (starting with SKL where they begin to diverge) use the CPU
codname with the microarchitecture name(s), which matter for hybrid as
there are multiple uarches.
I'd argue that this wants to become INTEL_DIAMONDRAPIDS_X (and CMT/DMT
to SRF/CWF), or all of SPR/EMR/GNR want to turn into GLC/RPC/RWC so
they're consistent when used together.
Thanks,
~Andrew
next prev parent reply other threads:[~2025-02-12 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 17:37 [PATCH] x86/cpu: Add two Intel CPU model numbers Tony Luck
2025-02-12 1:39 ` Andrew Cooper [this message]
2025-02-12 16:09 ` Luck, Tony
2025-02-14 13:02 ` Peter Zijlstra
2025-02-14 16:23 ` Dave Hansen
2025-02-14 17:17 ` Luck, Tony
2025-04-18 6:40 ` Ingo Molnar
2025-02-14 13:03 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 14:42 Christian Ludloff
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=c8545ed5-b822-43a0-a347-d077bccf9d6f@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--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