linux-kernel - Re: [PATCH v4 4/4] KVM: nVMX: Remove explicit filtering of GUEST_INTR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9d93f313-b329-4e64-a4ed-88e44be16689@intel.com>
Date: Fri, 16 Jan 2026 17:02:14 +0800
From: Xiaoyao Li <xiaoyao.li@...el.com>
To: Sean Christopherson <seanjc@...gle.com>,
 Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
 Chao Gao <chao.gao@...el.com>, Xin Li <xin@...or.com>,
 Yosry Ahmed <yosry.ahmed@...ux.dev>
Subject: Re: [PATCH v4 4/4] KVM: nVMX: Remove explicit filtering of
 GUEST_INTR_STATUS from shadow VMCS fields

On 1/16/2026 1:34 AM, Sean Christopherson wrote:
> Drop KVM's filtering of GUEST_INTR_STATUS when generating the shadow VMCS
> bitmap now that KVM drops GUEST_INTR_STATUS from the set of supported
> vmcs12 fields if the field isn't supported by hardware, and initialization
> of the shadow VMCS fields omits unsupported vmcs12 fields.
> 
> Note, there is technically a small functional change here, as the vmcs12
> filtering only requires support for Virtual Interrupt Delivery, whereas
> the shadow VMCS code being removed required "full" APICv support, i.e.
> required Virtual Interrupt Delivery *and* APIC Register Virtualizaton *and*
> Posted Interrupt support.
> 
> Opportunistically tweak the comment to more precisely explain why the
> PML and VMX preemption timer fields need to be explicitly checked.
> 
> Signed-off-by: Sean Christopherson <seanjc@...gle.com>

Reviewed-by: Xiaoyao Li <xiaoyao.li@...el.com>