x86/hyperv: Allow 15-bit APIC IDs for VTL platforms
Subsystems (3)
PATCH v2 1/1 x86/hyperv: Allow 15-bit APIC IDs for VTL platforms
The current method for signaling the compatibility of a Hyper-V host with MSIs featuring 15-bit APIC IDs relies on a synthetic cpuid leaf. However, for higher VTLs, this leaf is not reported, due to the absence of an IO-APIC.
As an alternative, assume that when running at a high VTL, the host supports 15-bit APIC IDs. This assumption is safe, as Hyper-V does not employ any architectural MSIs at higher VTLs
This unblocks startup of VTL2 environments with more than 256 CPUs.
---
[V2]
- Modify commit message
arch/x86/hyperv/hv_vtl.c | 7 +++++++ 1 file changed, 7 insertions(+)
arch/x86/hyperv/hv_vtl.c +7 -0
@@ -16,6 +16,11 @@extern struct boot_params boot_params;static struct real_mode_header hv_vtl_real_mode_header; +static bool __init hv_vtl_msi_ext_dest_id (void ) +{ +return true; +} +void __init hv_vtl_init_platform (void ) {pr_info ("Linux runs in Hyper-V Virtual Trust Level\n" );
@@ -38,6 +43,8 @@ void __init hv_vtl_init_platform(void) x86_platform.legacy.warm_reset =0 ; x86_platform.legacy.reserve_bios_regions =0 ; x86_platform.legacy.devices.pnpbios =0 ; + + x86_init.hyper.msi_ext_dest_id = hv_vtl_msi_ext_dest_id; }static inline u64 hv_vtl_system_desc_base (struct ldttss_desc *desc)
Signature · 1 line
1.8.3.1
From: Saurabh Sengar <[email protected]> Sent: Monday, January 15, 2024 9:58 AM
Quoted 46 lines
The current method for signaling the compatibility of a Hyper-V host with MSIs featuring 15-bit APIC IDs relies on a synthetic cpuid leaf. However, for higher VTLs, this leaf is not reported, due to the absence of an IO-APIC.
As an alternative, assume that when running at a high VTL, the host supports 15-bit APIC IDs. This assumption is safe, as Hyper-V does not employ any architectural MSIs at higher VTLs
This unblocks startup of VTL2 environments with more than 256 CPUs.
Signed-off-by Saurabh Sengar <[email protected]>---
[V2]
- Modify commit messagearch/x86/hyperv/hv_vtl.c | 7 +++++++ 1 file changed, 7 insertions(+)arch/x86/hyperv/hv_vtl.c +7
-1@@ -16,6 +16,11 @@extern struct boot_params boot_params;static struct real_mode_header hv_vtl_real_mode_header; +static bool __init hv_vtl_msi_ext_dest_id (void ) +{ +return true; +} +void __init hv_vtl_init_platform (void ) {pr_info ("Linux runs in Hyper-V Virtual Trust Level\n" );@@ -38,6 +43,8 @@ void __init hv_vtl_init_platform(void) x86_platform.legacy.warm_reset =0 ; x86_platform.legacy.reserve_bios_regions =0 ; x86_platform.legacy.devices.pnpbios =0 ; + + x86_init.hyper.msi_ext_dest_id = hv_vtl_msi_ext_dest_id; }static inline u64 hv_vtl_system_desc_base (struct ldttss_desc *desc) --
Quoted 2 lines
1.8.3.1
Quoted 14 lines · Michael Kelley
From: Saurabh Sengar <[email protected]> Sent: Monday, January 15, 2024 9:58 AM
Quoted 13 lines
The current method for signaling the compatibility of a Hyper-V host with MSIs featuring 15-bit APIC IDs relies on a synthetic cpuid leaf. However, for higher VTLs, this leaf is not reported, due to the absence of an IO-APIC.
As an alternative, assume that when running at a high VTL, the host supports 15-bit APIC IDs. This assumption is safe, as Hyper-V does not employ any architectural MSIs at higher VTLs
This unblocks startup of VTL2 environments with more than 256 CPUs.
Signed-off-by Saurabh Sengar <[email protected]>
[...]
Quoted 2 lines
Reviewed-by Michael Kelley <[email protected]>
Applied. Thanks.