From: Tianyu Lan <ltykernel@gmail.com>
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, Neeraj.Upadhyay@amd.com, yuehaibing@huawei.com,
kvijayab@amd.com, jacob.jun.pan@linux.intel.com,
jpoimboe@kernel.org, tiala@microsoft.com
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 5/6] x86/Hyper-V: Not use auto-eoi when Secure AVIC is available
Date: Tue, 6 May 2025 09:07:10 -0400 [thread overview]
Message-ID: <20250506130712.156583-6-ltykernel@gmail.com> (raw)
In-Reply-To: <20250506130712.156583-1-ltykernel@gmail.com>
From: Tianyu Lan <tiala@microsoft.com>
Hyper-V doesn't support auto-eoi with Secure AVIC.
So Enable HV_DEPRECATING_AEOI_RECOMMENDED flag
to force to write eoi register after handling
interrupt.
Signed-off-by: Tianyu Lan <tiala@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;
+
if (ms_hyperv.hints & HV_X64_HYPERV_NESTED) {
hv_nested = true;
pr_info("Hyper-V: running on a nested hypervisor\n");
--
2.25.1
next prev parent reply other threads:[~2025-05-06 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 13:07 [RFC PATCH 0/6] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform Tianyu Lan
2025-05-06 13:07 ` [RFC PATCH 1/6] x86/Hyper-V: Not use hv apic driver when Secure AVIC is available Tianyu Lan
2025-05-14 16:54 ` Michael Kelley
2025-05-15 12:56 ` Tianyu Lan
2025-05-06 13:07 ` [RFC PATCH 2/6] x86/x2apic-savic: Expose x2apic_savic_update_vector() Tianyu Lan
2025-05-07 3:56 ` Neeraj Upadhyay
2025-05-07 16:15 ` Tianyu Lan
2025-05-06 13:07 ` [RFC PATCH 3/6] drivers/hv: Allow vmbus message synic interrupt injected from Hyper-V Tianyu Lan
2025-05-06 13:07 ` [RFC PATCH 4/6] x86/Hyper-V: Allow Hyper-V to inject Hyper-V vectors Tianyu Lan
2025-05-14 16:54 ` Michael Kelley
2025-05-16 15:39 ` Tianyu Lan
2025-05-06 13:07 ` Tianyu Lan [this message]
2025-05-14 16:54 ` [RFC PATCH 5/6] x86/Hyper-V: Not use auto-eoi when Secure AVIC is available Michael Kelley
2025-05-16 15:53 ` Tianyu Lan
2025-05-06 13:07 ` [RFC PATCH 6/6] x86/x2apic-savic: Not set APIC backing page if Secure AVIC is not enabled Tianyu Lan
2025-05-07 4:03 ` Neeraj Upadhyay
2025-05-16 15:58 ` Tianyu Lan
2025-05-14 16:54 ` [RFC PATCH 0/6] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform Michael Kelley
2025-05-15 12:51 ` Tianyu Lan
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=20250506130712.156583-6-ltykernel@gmail.com \
--to=ltykernel@gmail.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jpoimboe@kernel.org \
--cc=kvijayab@amd.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.