From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Chao Gao <chao.gao@intel.com>, Xin Li <xin@zytor.com>,
Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: Re: [PATCH v4 4/4] KVM: nVMX: Remove explicit filtering of GUEST_INTR_STATUS from shadow VMCS fields
Date: Fri, 16 Jan 2026 17:02:14 +0800 [thread overview]
Message-ID: <9d93f313-b329-4e64-a4ed-88e44be16689@intel.com> (raw)
In-Reply-To: <20260115173427.716021-5-seanjc@google.com>
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@google.com>
Reviewed-by: Xiaoyao Li <xiaoyao.li@intel.com>
next prev parent reply other threads:[~2026-01-16 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:34 [PATCH v4 0/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware" Sean Christopherson
2026-01-15 17:34 ` [PATCH v4 1/4] KVM: nVMX: Setup VMX MSRs on loading CPU during nested_vmx_hardware_setup() Sean Christopherson
2026-01-15 17:34 ` [PATCH v4 2/4] KVM: VMX: Add a wrapper around ROL16() to get a vmcs12 from a field encoding Sean Christopherson
2026-01-15 17:34 ` [PATCH v4 3/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware" Sean Christopherson
2026-01-16 8:59 ` Xiaoyao Li
2026-01-15 17:34 ` [PATCH v4 4/4] KVM: nVMX: Remove explicit filtering of GUEST_INTR_STATUS from shadow VMCS fields Sean Christopherson
2026-01-16 9:02 ` Xiaoyao Li [this message]
2026-02-04 0:10 ` [PATCH v4 0/4] KVM: nVMX: Disallow access to vmcs12 fields that aren't supported by "hardware" Sean Christopherson
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=9d93f313-b329-4e64-a4ed-88e44be16689@intel.com \
--to=xiaoyao.li@intel.com \
--cc=chao.gao@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=xin@zytor.com \
--cc=yosry.ahmed@linux.dev \
/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
all inboxes | Powered by JetHome®