mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Thomas Gleixner <tglx@kernel.org>,
	Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Tony Luck <tony.luck@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/bugs: Replace RFDS model checks with VFM ones
Date: Fri, 30 Oct 2026 21:20:08 -0700	[thread overview]
Message-ID: <20261031042008.GJauVseM2X4-dye4ra@fat_crate.local> (raw)
In-Reply-To: <20261030195214.1284995-1-sohil.mehta@intel.com>

On Fri, Oct 30, 2026 at 12:52:14PM -0700, Sohil Mehta wrote:
> The RFDS vulnerability check uses raw model numbers to identify Alder
> Lake and Raptor Lake. Most Intel-specific code has already moved away
> from x86_model checks, but this one got added recently.
> 
> Replace the x86_model checks with VFM ones to make them more readable.
> 
> Signed-off-by: Sohil Mehta <sohil.mehta@intel.com>
> ---
>  arch/x86/kernel/cpu/common.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index c7352827f491..8d7bd8bb7b18 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -1392,8 +1392,8 @@ static bool __init vulnerable_to_rfds(u64 x86_arch_cap_msr)
>  	 * both Core and Atom CPUs. Mark unaffected when Atom CPUs are not
>  	 * present.
>  	 */
> -	if ((boot_cpu_data.x86_model == 0x97 ||
> -	     boot_cpu_data.x86_model == 0xB7) &&
> +	if ((boot_cpu_data.x86_vfm == INTEL_ALDERLAKE ||
> +	     boot_cpu_data.x86_vfm == INTEL_RAPTORLAKE) &&
>  	     boot_cpu_data.topo.intel_type != INTEL_CPU_TYPE_ATOM &&
>  	     !boot_cpu_has(X86_FEATURE_HYBRID_CPU))
>  		return false;
> -- 

Queued, thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2026-10-31  4:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 19:52 Sohil Mehta
2026-10-30 21:50 ` Pawan Gupta
2026-10-31  4:20 ` Borislav Petkov [this message]
2026-11-02  3:56 ` [tip: x86/urgent] " tip-bot2 for Sohil Mehta
2026-11-02  4:31 ` [tip: x86/cleanups] " tip-bot2 for Sohil Mehta

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=20261031042008.GJauVseM2X4-dye4ra@fat_crate.local \
    --to=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@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®