diff options
| author | Juergen Gross <jgross@suse.com> | 2024-04-05 14:15:47 +0200 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com> | 2024-05-02 19:18:44 +0200 |
| commit | 802600ebdf23371b893a51a4ad046213f112ea3b (patch) | |
| tree | 00558998dbf10f83fc376e1568bc12e143e12d27 /fs | |
| parent | 8a95db3bf8a32186fe448b1a934afbd5f1da0263 (diff) | |
| download | linux-802600ebdf23371b893a51a4ad046213f112ea3b.tar.gz linux-802600ebdf23371b893a51a4ad046213f112ea3b.tar.bz2 linux-802600ebdf23371b893a51a4ad046213f112ea3b.zip | |
x86/xen: return a sane initial apic id when running as PV guest
With recent sanity checks for topology information added, there are now
warnings issued for APs when running as a Xen PV guest:
[Firmware Bug]: CPU 1: APIC ID mismatch. CPUID: 0x0000 APIC: 0x0001
This is due to the initial APIC ID obtained via CPUID for PV guests is
always 0.
Avoid the warnings by synthesizing the CPUID data to contain the same
initial APIC ID as xen_pv_smp_config() is using for registering the
APIC IDs of all CPUs.
Fixes: 52128a7a21f7 ("86/cpu/topology: Make the APIC mismatch warnings complete")
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions