Re: [RFC PATCH v3 00/27] KVM: SVM: Add support for SEV-SNP Secure AVIC

[Naveen N Rao <naveen@kernel.org>]

On Wed, Jul 08, 2026 at 12:01:58PM +0530, Naveen N Rao (AMD) wrote:
> This is RFC v3 of the patches adding KVM support for Secure AVIC. RFC v2:
> http://lore.kernel.org/r/20250923050317.205482-1-Neeraj.Upadhyay@amd.com
> 
> There are significant changes throughout the series since the last RFC, 
> with some of the highlights being:
> - Integrate with AVIC code since Secure AVIC is APICv, but for protected 
>   APIC guests. This aligns with TDX which also requires APICv and 
>   enables reuse of APICv code paths in KVM. Patches #8 to #14.
> - Mandate use of split irqchip, and drop changes related to the KVM 
>   IOAPIC. KVM PIC/PIT can't be supported (described more fully in the 
>   commit log of the relevant patches). Patch #24.
> - Enable use of SVM_AVIC_INCOMPLETE_IPI VMGEXIT for vCPU notification 
>   request from the guest. Patch #22.
> - Utilize vNMI injection path for NMI handling. Patch #23.
> - Introduce a new kvm_x86_op to distinguish need for injectable 
>   interrupts vs. IPI notifications. Patches #18 and #19.
> - Retain KVM PV ops, and instead require guests to opt-in/disable.  
>   Patch #3.
> 
> Patches #1 to #4 are changes to the guest x2APIC Secure AVIC driver.

I missed mentioning one of the main TODOs on which I am looking for 
suggestions on: handling SVM_VMGEXIT_SAVIC_REGISTER_GPA and ensuring 
that Secure AVIC backing page accesses by the guest do not cause #NPF.  
Patch #16 has the details.

And it looks like I also goofed up Neeraj's email address - sorry! (Now 
fixed)



- Naveen