From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Kai Huang <kai.huang@intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>
Subject: [PATCH v2 0/2] KVM: VMX: Handle SEAMCALL or TDCALL VM-Exits
Date: Thu, 16 Oct 2025 11:21:46 -0700 [thread overview]
Message-ID: <20251016182148.69085-1-seanjc@google.com> (raw)
Add VM-Exit handlers for SEAMCALL and TDCALL as the instructions are gated
only by VMXON, and so a buggy/misbehaving guest will likely be terminated
(because KVM bails with KVM_INTERNAL_ERROR_UNEXPECTED_EXIT_REASON) if the
guest executes SEAMCALL or TDCALL.
v2:
- Apply the behavior only to VMX. KVM can't inject #UDs for TDX, and the
TDX-Module is supposed to handle SEAMCALL. [Chao]
- Fix nested exit handling (inverted return). [Xiaoyao]
- WARN if the TDX-Module punts a SEAMCALL exit to KVM. [Xiaoyao]
- Fix typos. [Binbin]
v1: https://lore.kernel.org/all/20251014231042.1399849-1-seanjc@google.com
Sean Christopherson (2):
KVM: VMX: Inject #UD if guest tries to execute SEAMCALL or TDCALL
KVM: TDX: WARN if a SEAMCALL VM-Exit makes its way out to KVM
arch/x86/include/uapi/asm/vmx.h | 1 +
arch/x86/kvm/vmx/nested.c | 8 ++++++++
arch/x86/kvm/vmx/tdx.c | 3 +++
arch/x86/kvm/vmx/vmx.c | 8 ++++++++
4 files changed, 20 insertions(+)
base-commit: 6b36119b94d0b2bb8cea9d512017efafd461d6ac
--
2.51.0.858.gf9c4a03a3a-goog
next reply other threads:[~2025-10-16 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:21 Sean Christopherson [this message]
2025-10-16 18:21 ` [PATCH v2 1/2] KVM: VMX: Inject #UD if guest tries to execute SEAMCALL or TDCALL Sean Christopherson
2025-10-17 2:53 ` Xiaoyao Li
2025-10-17 5:27 ` Binbin Wu
2025-10-17 10:53 ` Huang, Kai
2025-10-17 13:00 ` Sean Christopherson
2025-10-17 20:34 ` Huang, Kai
2025-10-17 20:34 ` Huang, Kai
2025-10-16 18:21 ` [PATCH v2 2/2] KVM: TDX: WARN if a SEAMCALL VM-Exit makes its way out to KVM Sean Christopherson
2025-10-17 2:56 ` Xiaoyao Li
2025-10-17 5:29 ` Binbin Wu
2025-10-17 10:40 ` Huang, Kai
2025-10-17 17:25 ` Sean Christopherson
2025-10-17 20:58 ` Huang, Kai
2025-10-17 21:11 ` Huang, Kai
2025-10-20 6:10 ` Xiaoyao Li
2025-10-20 15:03 ` Sean Christopherson
2025-11-04 17:45 ` [PATCH v2 0/2] KVM: VMX: Handle SEAMCALL or TDCALL VM-Exits 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=20251016182148.69085-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=xiaoyao.li@intel.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