The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xiaoyao.li@intel.com
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org, mingo@redhat.com, tglx@kernel.org,
	x86@kernel.org
Subject: Re: [PATCH] x86/microcode: Fix comment in microcode_loader_disabled()
Date: Wed, 13 May 2026 00:23:59 +0100	[thread overview]
Message-ID: <204b6126-e780-401b-8a6f-6beb84bc43ae@citrix.com> (raw)
In-Reply-To: <20260512152754.671760-1-xiaoyao.li@intel.com>

> diff --git a/arch/x86/kernel/cpu/microcode/core.c
> b/arch/x86/kernel/cpu/microcode/core.c index
> 651202e6fefb..68a1a893246c 100644 ---
> a/arch/x86/kernel/cpu/microcode/core.c +++
> b/arch/x86/kernel/cpu/microcode/core.c @@ -126,7 +126,7 @@ bool __init
> microcode_loader_disabled(void)  	}
>  
>  	/*
> - * 2) Bit 31 in CPUID[1]:ECX is clear + * 2) Bit 31 in CPUID[1]:ECX
> is set  	 *    The bit is reserved for hypervisor use. This is still not
>  	 *    completely accurate as XEN PV guests don't see that CPUID bit
>  	 *    set, but that's good enough as they don't land on the BSP

The disposition of that bit isn't the only wrong thing.

That claim wasn't reviewed by anyone from Xen, and I don't even know
what "doesn't land on the BSP" is supposed to mean in context.

On AMD systems, the Hypervisor bit will always be present.  On any Intel
system since IvyBridge, the same is true.

But the logic is buggy and should use regular CPUID not native CPUID.

~Andrew

      parent reply	other threads:[~2026-05-12 23:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 15:27 [PATCH] x86/microcode: Fix comment in microcode_loader_disabled() Xiaoyao Li
2026-05-12 16:39 ` [tip: x86/microcode] " tip-bot2 for Xiaoyao Li
2026-05-12 23:23 ` Andrew Cooper [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=204b6126-e780-401b-8a6f-6beb84bc43ae@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@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