From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Borislav Petkov <bp@alien8.de>, Binbin Wu <binbin.wu@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org, dave.hansen@intel.com, seanjc@google.com,
pbonzini@redhat.com, kas@kernel.org, rick.p.edgecombe@intel.com,
vishal.l.verma@intel.com, chao.gao@intel.com
Subject: Re: [PATCH 1/2] x86/microcode: Do not access MSR_IA32_PLATFORM_ID when running as a guest
Date: Thu, 14 May 2026 20:38:20 +0800 [thread overview]
Message-ID: <2df97245-c1e7-4d72-9ab3-6c186b6c030f@intel.com> (raw)
In-Reply-To: <20260513200601.GMagTZqT_CT6EvN1Uz@fat_crate.local>
On 5/14/2026 4:06 AM, Borislav Petkov wrote:
> Patch in Fixes: causes the usual:
>
> unchecked MSR access error: RDMSR from 0x17 at ... (intel_get_platform_id)
> Call Trace:
> early_init_intel
> early_cpu_init
> setup_arch
> _printk
> start_kernel
> x86_64_start_reservations
> x86_64_start_kernel
> common_startup_64
>
> because the kernel is booted in a guest.
>
> In order to avoid it, this MSR access needs to be prevented when running
> virtualized. That is usually done by checking X86_FEATURE_HYPERVISOR but
> for this particular case it is too early yet.
>
> The platform ID needs to be read as early as when microcode is loaded on
> the BSP:
>
> load_ucode_bsp ... -> get_microcode_blob ... -> intel_find_matching_signature
>
> and by that time, CPUID leafs haven't been parsed yet.
>
> The microcode loader already has logic to check early whether the kernel
> is running virtualized so make that globally available to arch/x86/. The
> query whether running virtualized is getting more and more prominent in
> recent times so might as well make it an arch-global var which the rest
> of the code can use.
>
> Fixes: d8630b67ca1ed ("x86/cpu: Add platform ID to CPU info structure")
> Reported-by: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Tested-by: Binbin Wu <binbin.wu@linux.intel.com>
> Link: https://lore.kernel.org/r/20260430020953.1405535-1-binbin.wu@linux.intel.com
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
> @@ -179,6 +172,11 @@ void __init load_ucode_bsp(void)
>
> early_parse_cmdline();
>
> + if (!cpuid_feature())
> + dis_ucode_ldr = true;
> + else
> + x86_hypervisor_present = native_cpuid_ecx(1) & BIT(31);
> +
IIUC, the reason why move the initialization of x86_hypervisor_present
from microcode_loader_disabled to here is to make sure
x86_hypervisor_present is always initialized, right?
But initializing x86_hypervisor_present by load_ucode_bsp() depends on
CONFIG_MICROCODE, which depends on CPU_SUP_AMD || CPU_SUP_INTEL. So when
both CPU_SUP_AMD and CPU_SUP_INTEL are not enabled,
x86_hypervisor_present will always be 0. It's not a problem for now, we
can solve it when x86_hypervisor_present is going to be used by CENTAUR
or ZHAOXIN.
next prev parent reply other threads:[~2026-05-14 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260430020953.1405535-1-binbin.wu@linux.intel.com>
2026-05-11 9:38 ` [PATCH v2] x86/cpu: Skip reading MSR_IA32_PLATFORM_ID in virtualized environment Kiryl Shutsemau
2026-05-11 10:04 ` Borislav Petkov
2026-05-12 1:57 ` Binbin Wu
2026-05-13 10:14 ` Borislav Petkov
2026-05-13 11:02 ` Binbin Wu
2026-05-13 11:08 ` Borislav Petkov
2026-05-13 12:20 ` Binbin Wu
2026-05-13 13:11 ` Borislav Petkov
2026-05-13 14:41 ` Binbin Wu
2026-05-13 20:00 ` Borislav Petkov
2026-05-13 20:06 ` [PATCH 1/2] x86/microcode: Do not access MSR_IA32_PLATFORM_ID when running as a guest Borislav Petkov
2026-05-14 6:22 ` Binbin Wu
2026-05-14 10:40 ` Borislav Petkov
2026-05-14 12:38 ` Xiaoyao Li [this message]
2026-05-14 14:13 ` Borislav Petkov
2026-05-13 20:07 ` [PATCH 2/2] x86/cpu: Move intel_get_platform_id() to cpu/intel.c Borislav Petkov
2026-05-14 6:25 ` Binbin Wu
2026-05-14 12:39 ` Xiaoyao Li
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=2df97245-c1e7-4d72-9ab3-6c186b6c030f@intel.com \
--to=xiaoyao.li@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@intel.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=vishal.l.verma@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