[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260112174535.3132800-1-chengkev@google.com>
Date: Mon, 12 Jan 2026 17:45:30 +0000
From: Kevin Cheng <chengkev@...gle.com>
To: seanjc@...gle.com, pbonzini@...hat.com
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, yosry.ahmed@...ux.dev,
Kevin Cheng <chengkev@...gle.com>
Subject: [PATCH V2 0/5] Align SVM with APM defined behaviors
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
Powered by blists - more mailing lists