mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, sohil.mehta@intel.com,
	zhao1.liu@intel.com, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Jon Kohler <jon@nutanix.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Thomas Gleixner <tglx@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	x86@kernel.org
Subject: Re: [PATCH v4 2/4] x86/cpu: Add platform ID to CPU info structure
Date: Wed, 4 Mar 2026 18:26:36 -0800	[thread overview]
Message-ID: <20260305022636.pt4zt42qjiudxtbz@desk> (raw)
In-Reply-To: <20260304181020.8D518228@davehans-spike.ostc.intel.com>

On Wed, Mar 04, 2026 at 10:10:20AM -0800, Dave Hansen wrote:
> 
> From: Dave Hansen <dave.hansen@linux.intel.com>
> 
> The end goal here is to be able to do x86_match_cpu() and match on a
> specific platform ID. While it would be possible to stash this ID
> off somewhere or read it dynamically, that approaches would not be
> consistent with the other fields which can be matched.
> 
> Read the platform ID and store it in cpuinfo_x86.
> 
> There are lots of sites to set this new field. Place it near
> the place c->microcode is established since the platform ID is
> so closely intertwined with microcode updates.
> 
> Note: This should not grow the size of 'struct cpuinfo_x86' in
> practice since the u8 fits next to another u8 in the structure.
> 
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> Cc: Thomas Gleixner <tglx@kernel.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
> Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>
> Cc: x86@kernel.org
> Cc: Jon Kohler <jon@nutanix.com>
> 
> --
> 
> Changes from v2:
>  * rename x86_platform_id=>intel_platform_id and remove
>    initialization from generic code
>  * Add a amd_unused so it's clear the AMD folks have a
>    free field to play with.
> ---
> 
>  b/arch/x86/include/asm/microcode.h      |    2 ++
>  b/arch/x86/include/asm/processor.h      |    5 +++++
>  b/arch/x86/kernel/cpu/intel.c           |    1 +
>  b/arch/x86/kernel/cpu/microcode/intel.c |    2 +-
>  4 files changed, 9 insertions(+), 1 deletion(-)
> 
> diff -puN arch/x86/include/asm/microcode.h~cpu-x86_stepping arch/x86/include/asm/microcode.h
> --- a/arch/x86/include/asm/microcode.h~cpu-x86_stepping	2026-02-24 15:37:21.947261472 -0800
> +++ b/arch/x86/include/asm/microcode.h	2026-02-24 15:37:21.955261858 -0800
> @@ -61,6 +61,8 @@ static inline int intel_microcode_get_da
>  	return hdr->datasize ? : DEFAULT_UCODE_DATASIZE;
>  }
>  
> +extern u32 intel_get_platform_id(void);
> +
>  static inline u32 intel_get_microcode_revision(void)
>  {
>  	u32 rev, dummy;
> diff -puN arch/x86/include/asm/processor.h~cpu-x86_stepping arch/x86/include/asm/processor.h
> --- a/arch/x86/include/asm/processor.h~cpu-x86_stepping	2026-02-24 15:37:21.949261568 -0800
> +++ b/arch/x86/include/asm/processor.h	2026-02-24 15:37:21.955261858 -0800
> @@ -140,6 +140,11 @@ struct cpuinfo_x86 {
>  		__u32		x86_vfm;
>  	};
>  	__u8			x86_stepping;
> +	union {
> +		// MSR_IA32_PLATFORM_ID[52-50]
> +		__u8			intel_platform_id;
> +		__u8			amd_unused;
> +	};
>  #ifdef CONFIG_X86_64
>  	/* Number of 4K pages in DTLB/ITLB combined(in pages): */
>  	int			x86_tlbsize;
> diff -puN arch/x86/kernel/cpu/intel.c~cpu-x86_stepping arch/x86/kernel/cpu/intel.c
> --- a/arch/x86/kernel/cpu/intel.c~cpu-x86_stepping	2026-02-24 15:37:21.950261617 -0800
> +++ b/arch/x86/kernel/cpu/intel.c	2026-02-24 15:37:21.955261858 -0800
> @@ -205,6 +205,7 @@ static void early_init_intel(struct cpui
>  
>  	if (c->x86 >= 6 && !cpu_has(c, X86_FEATURE_IA64))
>  		c->microcode = intel_get_microcode_revision();
> +	c->intel_platform_id = intel_get_platform_id();

Just want to make sure that c->intel_platform_id not getting explicitly
initialized for !CONFIG_CPU_SUP_INTEL is okay. I believe it is fine because
the global boot_cpu_data should be zero-initialized.

I see model and stepping are being initialized in identify_cpu(), but I
don't see any vendor specific initialization here:

identify_cpu()
{
        int i;

        c->loops_per_jiffy = loops_per_jiffy;
        c->x86_cache_size = 0;
        c->x86_vendor = X86_VENDOR_UNKNOWN;
        c->x86_model = c->x86_stepping = 0;     /* So far unknown... */

Reviewed-by: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>

  reply	other threads:[~2026-03-05  2:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 18:10 [PATCH v4 0/4] x86/cpu: Take Intel platform into account for old microcode checks Dave Hansen
2026-03-04 18:10 ` [PATCH v4 1/4] x86/microcode: Refactor platform ID enumeration into a helper Dave Hansen
2026-03-05  1:38   ` Pawan Gupta
2026-03-05  6:28     ` Sohil Mehta
2026-03-05 18:01       ` Pawan Gupta
2026-03-05 18:37     ` Dave Hansen
2026-03-05 13:16   ` Borislav Petkov
2026-03-05 19:07   ` [tip: x86/microcode] " tip-bot2 for Dave Hansen
2026-03-05 20:28   ` tip-bot2 for Dave Hansen
2026-03-04 18:10 ` [PATCH v4 2/4] x86/cpu: Add platform ID to CPU info structure Dave Hansen
2026-03-05  2:26   ` Pawan Gupta [this message]
2026-03-05 18:39     ` Dave Hansen
2026-03-05 19:07   ` [tip: x86/microcode] " tip-bot2 for Dave Hansen
2026-03-05 20:28   ` tip-bot2 for Dave Hansen
     [not found]   ` <20260306004923.ln6ai2zl23gjsdov@desk>
2026-03-06  0:56     ` [PATCH v4 2/4] " Pawan Gupta
2026-03-04 18:10 ` [PATCH v4 3/4] x86/cpu: Add platform ID to CPU matching structure Dave Hansen
2026-03-05 19:07   ` [tip: x86/microcode] " tip-bot2 for Dave Hansen
2026-03-05 20:28   ` tip-bot2 for Dave Hansen
2026-03-04 18:10 ` [PATCH v4 4/4] x86/microcode: Add platform mask to Intel microcode "old" list Dave Hansen
2026-03-05 19:07   ` [tip: x86/microcode] " tip-bot2 for Dave Hansen
2026-03-05 20:28   ` tip-bot2 for Dave Hansen

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=20260305022636.pt4zt42qjiudxtbz@desk \
    --to=pawan.kumar.gupta@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jon@nutanix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=zhao1.liu@intel.com \
    /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®