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, arnd@arndb.de, Neeraj.Upadhyay@amd.com,
tiala@microsoft.com, kvijayab@amd.com,
romank@linux.microsoft.com
Cc: linux-arch@vger.kernel.org, linux-hyperv@vger.kernel.org
Subject: [PATCH 0/5] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform
Date: Thu, 18 Sep 2025 11:00:18 -0400 [thread overview]
Message-ID: <20250918150023.474021-1-tiala@microsoft.com> (raw)
Secure AVIC is a new hardware feature in the AMD64
architecture to allow SEV-SNP guests to prevent the
hypervisor from generating unexpected interrupts to
a vCPU or otherwise violate architectural assumptions
around APIC behavior.
Each vCPU has a guest-allocated APIC backing page of
size 4K, which maintains APIC state for that vCPU.
APIC backing page's ALLOWED_IRR field indicates the
interrupt vectors which the guest allows the hypervisor
to send.
This patchset is to enable the feature for Hyper-V
platform. Patch "Drivers: hv: Allow vmbus message
synic interrupt injected from Hyper-V" is to expose
new fucntion hv_enable_coco_interrupt() and device
driver and arch code may update AVIC backing page
ALLOWED_IRR field to allow Hyper-V inject associated
vector.
The patchset is based on the tip tree commit 27a17e02418e
(x86/sev: Indicate the SEV-SNP guest supports Secure AVIC)
Tianyu Lan (5):
x86/hyperv: Don't use hv apic driver when Secure AVIC is available
drivers: hv: Allow vmbus message synic interrupt injected from Hyper-V
x86/hyperv: Don't use auto-eoi when Secure AVIC is available
x86/hyperv: Allow Hyper-V to inject STIMER0 interrupts
x86/Hyper-V: Add Hyper-V specific hvcall to set backing page
arch/x86/hyperv/hv_apic.c | 8 ++++++
arch/x86/hyperv/hv_init.c | 31 ++++++++++++++++++++++-
arch/x86/hyperv/ivm.c | 38 ++++++++++++++++++++++++++++
arch/x86/include/asm/mshyperv.h | 2 ++
arch/x86/kernel/apic/x2apic_savic.c | 9 ++++++-
arch/x86/kernel/cpu/mshyperv.c | 3 +++
drivers/hv/hv.c | 2 ++
drivers/hv/hv_common.c | 5 ++++
include/asm-generic/mshyperv.h | 1 +
include/hyperv/hvgdk_mini.h | 39 +++++++++++++++++++++++++++++
10 files changed, 136 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2025-09-18 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 15:00 Tianyu Lan [this message]
2025-09-18 15:00 ` [PATCH 1/5] x86/hyperv: Don't use hv apic driver when Secure AVIC is available Tianyu Lan
2025-09-18 15:00 ` [PATCH 2/5] drivers: hv: Allow vmbus message synic interrupt injected from Hyper-V Tianyu Lan
2025-09-18 15:00 ` [PATCH 3/5] x86/hyperv: Don't use auto-eoi when Secure AVIC is available Tianyu Lan
2025-09-18 15:00 ` [PATCH 4/5] x86/hyperv: Allow Hyper-V to inject STIMER0 interrupts Tianyu Lan
2025-09-18 15:00 ` [PATCH 5/5] x86/Hyper-V: Add Hyper-V specific hvcall to set backing page Tianyu Lan
2025-09-18 15:09 ` Borislav Petkov
2025-09-18 17:11 ` Tianyu Lan
2025-09-18 19:59 ` Borislav Petkov
2025-09-30 23:05 ` [PATCH 0/5] x86/Hyper-V: Add AMD Secure AVIC for Hyper-V platform Wei Liu
2025-10-13 17:18 ` Wei Liu
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=20250918150023.474021-1-tiala@microsoft.com \
--to=ltykernel@gmail.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kvijayab@amd.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=romank@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=tiala@microsoft.com \
--cc=wei.liu@kernel.org \
--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