From: Tianyu Lan <ltyker...@gmail.com> Sent: Tuesday, May 6, 2025 6:07 AM
>
For the patch Subject, use:
x86/hyperv: Don't use auto-EOI when Secure AVIC is available
> Hyper-V doesn't support auto-eoi with Secure AVIC.
> So Enable HV_DEPRECATING_AEOI_RECOMMENDED flag
s/Enable/enable/
> to force to write eoi register after handling interrupt.
"to force writing the EOI register after handling an interrupt."
>
> Signed-off-by: Tianyu Lan <ti...@microsoft.com>
> ---
> arch/x86/kernel/cpu/mshyperv.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/kernel/cpu/mshyperv.c b/arch/x86/kernel/cpu/mshyperv.c
> index 3e2533954675..fbe45b5e9790 100644
> --- a/arch/x86/kernel/cpu/mshyperv.c
> +++ b/arch/x86/kernel/cpu/mshyperv.c
> @@ -463,6 +463,9 @@ static void __init ms_hyperv_init_platform(void)
>
> hv_identify_partition_type();
>
> + if (cc_platform_has(CC_ATTR_SNP_SECURE_AVIC))
> + ms_hyperv.hints |= HV_DEPRECATING_AEOI_RECOMMENDED;
> +
Shouldn't Hyper-V already be setting this flag if it is offering Secure AVIC
to guests? I guess it doesn't hurt to do this in the Linux code, but it seems
like it should be Hyper-V's responsibility.
Michael
> if (ms_hyperv.hints & HV_X64_HYPERV_NESTED) {
> hv_nested = true;
> pr_info("Hyper-V: running on a nested hypervisor\n");
> --
> 2.25.1
>
