public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Tony Luck <tony.luck@intel.com>, <x86@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>
Cc: <linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [PATCH] x86/cpu: Add CPU model numbers for Novalake
Date: Fri, 1 Aug 2025 17:06:47 -0700	[thread overview]
Message-ID: <810fa3f0-8cca-451b-8bbd-b9bbabfe0b4b@intel.com> (raw)
In-Reply-To: <20250801160028.4799-1-tony.luck@intel.com>

On 8/1/2025 9:00 AM, Tony Luck wrote:

> diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h
> index 5367dcbf5b30..e345dbdf933e 100644
> --- a/arch/x86/include/asm/intel-family.h
> +++ b/arch/x86/include/asm/intel-family.h
> @@ -152,6 +152,9 @@
>  
>  #define INTEL_WILDCATLAKE_L		IFM(6, 0xD5)
>  
> +#define INTEL_NOVALAKE			IFM(18, 0x01)
> +#define INTEL_NOVALAKE_L		IFM(18, 0x03)
> +

Are we planning to add models from newer families closer to their
predecessors? I like the idea of continuing to group them by type. But,
it would inconvenience folks who are trying to find a name based on a
Family-model number. (I guess that would be a minority.)

Diamond rapids (Family 19) was added at the bottom of the file. Should
that be moved closer to its type?

Also, the /* Family 6 */ comment at the top is now misleading.

Dave had briefly suggested ordering the file based on Family, but I am
not sure if he still feels that way.

https://lore.kernel.org/lkml/40538b12-5929-4f05-b65e-8b807057abd5@intel.com/

>  /* "Small Core" Processors (Atom/E-Core) */
>  
>  #define INTEL_ATOM_BONNELL		IFM(6, 0x1C) /* Diamondville, Pineview */


      reply	other threads:[~2025-08-02  0:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 16:00 [PATCH] x86/cpu: Add CPU model numbers for Novalake Tony Luck
2025-08-02  0:06 ` Sohil Mehta [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=810fa3f0-8cca-451b-8bbd-b9bbabfe0b4b@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.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