All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: git@evalyngoemer.com
Cc: linux-kernel@vger.kernel.org, tglx@kernel.org, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	hpa@zytor.com, joe@perches.com
Subject: Re: [PATCH] platform/x86: handle Intel CPUs falsely reporting as GenuineIotel
Date: Sat, 4 Jul 2026 09:37:14 +0100	[thread overview]
Message-ID: <20260704093714.4d6aec22@pumpkin> (raw)
In-Reply-To: <20260704025147.585133-1-git@evalyngoemer.com>

On Fri,  3 Jul 2026 22:51:47 -0400
git@evalyngoemer.com wrote:

> From: Evalyn Goemer <git@evalyngoemer.com>
> 
> Certain Intel CPUs have a bit flipped in the CPUID string causing them
> to report as "GenuineIotel" leading to them potentially not being detected
> properly as an Intel CPU.

IIRC that's a BIOS bug.
A lot of that info is written in by the BIOS rather than being in the silicon.

	David

> 
> This patch fixes this by adding the "GenuineIotel" string to the
> intel_cpu_dev.c_ident array inside the arch/x86/kernel/cpu/intel.c file.
> 
> This issue can be found as existing here:
> https://github.com/InstLatx64/InstLatx64/blob/master/GenuineIotel/GenuineIotel00306C3_Haswell_CPUID5.txt
> https://web.archive.org/web/20150818115122/http://store.steampowered.com/hwsurvey/processormfg
> 
> Signed-off-by: Evalyn Goemer <git@evalyngoemer.com>
> ---
>  arch/x86/kernel/cpu/intel.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> index abb398433..a2dcd6d05 100644
> --- a/arch/x86/kernel/cpu/intel.c
> +++ b/arch/x86/kernel/cpu/intel.c
> @@ -713,7 +713,7 @@ static void intel_detect_tlb(struct cpuinfo_x86 *c)
>  
>  static const struct cpu_dev intel_cpu_dev = {
>  	.c_vendor	= "Intel",
> -	.c_ident	= { "GenuineIntel" },
> +	.c_ident	= { "GenuineIntel", "GenuineIotel" },
>  #ifdef CONFIG_X86_32
>  	.legacy_models = {
>  		{ .family = 4, .model_names =


  reply	other threads:[~2026-07-04  8:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04  2:51 [PATCH] platform/x86: handle Intel CPUs falsely reporting as GenuineIotel git
2026-07-04  8:37 ` David Laight [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-07-04  8:22 Christian Ludloff
2026-07-04  9:46 ` Evalyn Goemer
2026-07-04 17:00   ` Christian Ludloff
2026-07-04 18:15     ` Evalyn Goemer
2026-07-04 18:29       ` Borislav Petkov
2026-07-04 18:52         ` H. Peter Anvin
2026-07-04 19:23           ` Evalyn Goemer
2026-07-04 19:39       ` 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=20260704093714.4d6aec22@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=git@evalyngoemer.com \
    --cc=hpa@zytor.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.