Re: [PATCH 1/2] KVM: nSVM: Set NMI_VECTOR in synthesized NMI exit_int_info
From: Sean Christopherson
Date: Fri Nov 13 2026 - 10:29:01 EST
On Wed, 28 Oct 2026 06:26:52 -0700, Jim Mattson wrote:
> Include NMI_VECTOR (2) in the vector field when synthesizing exit_int_info
> for a pending injected NMI in nested_save_pending_event_to_vmcb12(),
> matching nested VMX's idt_vectoring_info_field synthesis and the APM.
>
> Per AMD's APM (Vol. 2, "Intercepts During IDT Interrupt Delivery", Figure
> "EXITINTINFO" and Table "Guest Exception or Interrupt Types", and "Event
> Injection"), bits 7:0 of EXITINTINFO hold the 8-bit IDT vector of the
> interrupt or exception, and injected events are recorded in EXITINTINFO as
> though they had occurred normally in the guest. Although hardware ignores
> EVENTINJ.VECTOR on VMRUN when TYPE is NMI, EXITINTINFO records vector 2
> (#NMI) if a #VMEXIT occurs during NMI delivery.
>
> [...]
Applied to kvm-x86 svm, thanks!
[1/2] KVM: nSVM: Set NMI_VECTOR in synthesized NMI exit_int_info
https://github.com/kvm-x86/linux/commit/894f03b50b7d
[2/2] KVM: SVM: Set NMI_VECTOR in event_inj in svm_inject_nmi()
https://github.com/kvm-x86/linux/commit/f04911c243b4
--
https://github.com/kvm-x86/linux/tree/next