From: Sean Christopherson <seanjc@google.com>
To: Mahmoud Abumandour <ma.mandourr@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] KVM: nVMX: Don't clobber VM-Entry instruction length on soft INTn exits
Date: Mon, 16 Nov 2026 14:38:42 -0800 [thread overview]
Message-ID: <avuF8vW3g_o1t5DM@seanjc-mac.roam.internal> (raw)
In-Reply-To: <20261116223033.3866283-1-ma.mandourr@gmail.com>
On Mon, Nov 16, 2026, Mahmoud Abumandour wrote:
> KVM writes the length of a soft INTn that L2 was vectoring at the time of a
> nested VM-Exit into vmcs12's VM-Entry instruction length instead of the VM-Exit
> instruction length.
>
> Patch 1 is there because Sashiko pointed out that prepare_vmcs12() overwrites
> the VM-exit instruction length that vmcs12_save_pending_event() saves for soft
> events.
>
> v3:
> - Rebased onto kvm-x86/next.
v2 still applies cleanly, there's no need to rebase. I realize it's been several
weeks since you posted v2, but the reality is that everyone and their mother is
using AI to send patches right now, and so anything that isn't affecting real world
use cases is very low priority. Sorry.
TL;DR: please be patient.
prev parent reply other threads:[~2026-11-16 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 22:30 Mahmoud Abumandour
2026-11-16 22:30 ` [PATCH v3 1/3] KVM: nVMX: Fill VM-Exit instruction length before saving pending event Mahmoud Abumandour
2026-11-16 22:30 ` [PATCH v3 2/3] KVM: nVMX: Don't clobber VM-Entry instruction length when saving soft INTn Mahmoud Abumandour
2026-11-16 22:30 ` [PATCH v3 3/3] KVM: selftests: Verify nested VM-Exits while vectoring INT3 and INTn Mahmoud Abumandour
2026-11-16 22:38 ` Sean Christopherson [this message]
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=avuF8vW3g_o1t5DM@seanjc-mac.roam.internal \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ma.mandourr@gmail.com \
--cc=pbonzini@redhat.com \
/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®