On Tue, Sep 30, 2025 at 11:05:34PM +0000, Wei Liu wrote: > On Thu, Sep 18, 2025 at 11:00:18AM -0400, Tianyu Lan wrote: > > 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 > > These look good to me.
I applied these four to hyperv-next. > > > x86/Hyper-V: Add Hyper-V specific hvcall to set backing page > > Please address Borislav's comment on this patch. This is no longer needed. Thanks, Wei
