From: Kevin Cheng <chengkev@google.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
yosry.ahmed@linux.dev, Kevin Cheng <chengkev@google.com>
Subject: [PATCH V2 0/5] Align SVM with APM defined behaviors
Date: Mon, 12 Jan 2026 17:45:30 +0000 [thread overview]
Message-ID: <20260112174535.3132800-1-chengkev@google.com> (raw)
The APM lists the following behaviors
- The VMRUN, VMLOAD, VMSAVE, CLGI, VMMCALL, and INVLPGA instructions
can be used when the EFER.SVME is set to 1; otherwise, these
instructions generate a #UD exception.
- If VMMCALL instruction is not intercepted, the instruction raises a
#UD exception.
- STGI instruction causes a #UD exception if SVM is not enabled and
neither SVM Lock nor the device exclusion vector (DEV) are
supported.
The patches in this series fix current SVM bugs that do not adhere to
the APM listed behaviors.
v1 -> v2:
- Split up the series into smaller more logical changes as suggested
by Sean
- Added patch for injecting #UD for STGI under APM defined conditions
as suggested by Sean
- Combined EFER.SVME=0 conditional with intel CPU logic in
svm_recalc_instruction_intercepts
v1: https://lore.kernel.org/all/20260106041250.2125920-1-chengkev@google.com/
Kevin Cheng (5):
KVM: SVM: Move STGI and CLGI intercept handling
KVM: SVM: Inject #UD for STGI if EFER.SVME=0 and SVM Lock and DEV are
not available
KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0
KVM: SVM: Recalc instructions intercepts when EFER.SVME is toggled
KVM: SVM: Raise #UD if VMMCALL instruction is not intercepted
arch/x86/kvm/svm/svm.c | 52 ++++++++++++++++++++++++++++++++++++------
1 file changed, 45 insertions(+), 7 deletions(-)
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-12 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 17:45 Kevin Cheng [this message]
2026-01-12 17:45 ` [PATCH V2 1/5] KVM: SVM: Move STGI and CLGI intercept handling Kevin Cheng
2026-01-12 20:37 ` Yosry Ahmed
2026-01-15 1:39 ` Sean Christopherson
2026-01-15 16:41 ` Yosry Ahmed
2026-01-15 17:00 ` Sean Christopherson
2026-01-15 17:05 ` Yosry Ahmed
2026-01-15 17:29 ` Sean Christopherson
2026-01-22 4:59 ` Kevin Cheng
2026-01-12 17:45 ` [PATCH V2 2/5] KVM: SVM: Inject #UD for STGI if EFER.SVME=0 and SVM Lock and DEV are not available Kevin Cheng
2026-01-12 20:50 ` Yosry Ahmed
2026-01-22 5:02 ` Kevin Cheng
2026-01-12 17:45 ` [PATCH V2 3/5] KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0 Kevin Cheng
2026-01-12 20:51 ` Yosry Ahmed
2026-01-12 17:45 ` [PATCH V2 4/5] KVM: SVM: Recalc instructions intercepts when EFER.SVME is toggled Kevin Cheng
2026-01-12 17:45 ` [PATCH V2 5/5] KVM: SVM: Raise #UD if VMMCALL instruction is not intercepted Kevin Cheng
2026-01-12 20:54 ` Yosry Ahmed
2026-01-14 5:20 ` Manali Shukla
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=20260112174535.3132800-1-chengkev@google.com \
--to=chengkev@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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