From: Kevin Cheng <chengkev@google.com>
To: kvm@vger.kernel.org
Cc: yosryahmed@google.com, andrew.jones@linux.dev, thuth@redhat.com,
pbonzini@redhat.com, seanjc@google.com,
Kevin Cheng <chengkev@google.com>
Subject: [kvm-unit-tests PATCH] x86/svm: Add unsupported instruction intercept test
Date: Fri, 5 Dec 2025 08:02:28 +0000 [thread overview]
Message-ID: <20251205080228.4055341-3-chengkev@google.com> (raw)
In-Reply-To: <20251205080228.4055341-1-chengkev@google.com>
Add tests that expect a nested vm exit, due to an unsupported
instruction, to be handled by L0 even if L1 intercepts are set for that
instruction.
The new test exercises bug fixed by:
https://lore.kernel.org/all/20251205070630.4013452-1-chengkev@google.com/
Signed-off-by: Kevin Cheng <chengkev@google.com>
---
x86/svm.h | 5 +++-
x86/svm_tests.c | 75 +++++++++++++++++++++++++++++++++++++++++++++++
x86/unittests.cfg | 9 +++++-
3 files changed, 87 insertions(+), 2 deletions(-)
diff --git a/x86/svm.h b/x86/svm.h
index 93ef6f772c6ee..86d58c3100275 100644
--- a/x86/svm.h
+++ b/x86/svm.h
@@ -406,7 +406,10 @@ struct __attribute__ ((__packed__)) vmcb {
#define SVM_EXIT_MONITOR 0x08a
#define SVM_EXIT_MWAIT 0x08b
#define SVM_EXIT_MWAIT_COND 0x08c
-#define SVM_EXIT_NPF 0x400
+#define SVM_EXIT_XSETBV 0x08d
+#define SVM_EXIT_RDPRU 0x08e
+#define SVM_EXIT_INVPCID 0x0a2
+#define SVM_EXIT_NPF 0x400
#define SVM_EXIT_ERR -1
diff --git a/x86/svm_tests.c b/x86/svm_tests.c
index ccc89d45d4db9..cea8865787545 100644
--- a/x86/svm_tests.c
+++ b/x86/svm_tests.c
@@ -3572,6 +3572,80 @@ static void svm_shutdown_intercept_test(void)
report(vmcb->control.exit_code == SVM_EXIT_SHUTDOWN, "shutdown test passed");
}
+struct InvpcidDesc {
+ uint64_t pcid : 12;
+ uint64_t reserved : 52;
+ uint64_t addr;
+};
+
+static void insn_invpcid(struct svm_test *test)
+{
+ struct InvpcidDesc desc = {0};
+ unsigned long type = 0;
+
+ __asm__ volatile (
+ "invpcid %1, %0"
+ :
+ : "r" (type), "m" (desc)
+ : "memory"
+ );
+}
+
+asm(
+ "insn_rdtscp: rdtscp;ret\n\t"
+ "insn_skinit: skinit;ret\n\t"
+ "insn_xsetbv: xor %eax, %eax; xor %edx, %edx; xor %ecx, %ecx; xsetbv;ret\n\t"
+ "insn_rdpru: xor %ecx, %ecx; rdpru;ret\n\t"
+);
+
+extern void insn_rdtscp(struct svm_test *test);
+extern void insn_skinit(struct svm_test *test);
+extern void insn_xsetbv(struct svm_test *test);
+extern void insn_rdpru(struct svm_test *test);
+
+struct insn_table {
+ const char *name;
+ u64 intercept;
+ void (*insn_func)(struct svm_test *test);
+ u32 reason;
+};
+
+static struct insn_table insn_table[] = {
+ { "RDTSCP", INTERCEPT_RDTSCP, insn_rdtscp, SVM_EXIT_RDTSCP},
+ { "SKINIT", INTERCEPT_SKINIT, insn_skinit, SVM_EXIT_SKINIT},
+ { "XSETBV", INTERCEPT_XSETBV, insn_xsetbv, SVM_EXIT_XSETBV},
+ { "RDPRU", INTERCEPT_RDPRU, insn_rdpru, SVM_EXIT_RDPRU},
+ { "INVPCID", INTERCEPT_INVPCID, insn_invpcid, SVM_EXIT_INVPCID},
+ { NULL },
+};
+
+/*
+ * Test that L1 does not intercept instructions that are not advertised in
+ * guest CPUID.
+ */
+static void svm_unsupported_instruction_intercept_test(void)
+{
+ u32 cur_insn;
+ u32 exit_code;
+
+ vmcb_set_intercept(INTERCEPT_EXCEPTION_OFFSET + UD_VECTOR);
+
+ for (cur_insn = 0; insn_table[cur_insn].name != NULL; ++cur_insn) {
+ test_set_guest(insn_table[cur_insn].insn_func);
+ vmcb_set_intercept(insn_table[cur_insn].intercept);
+ svm_vmrun();
+ exit_code = vmcb->control.exit_code;
+
+ if (exit_code == SVM_EXIT_EXCP_BASE + UD_VECTOR)
+ report_pass("UD Exception injected");
+ else if (exit_code == insn_table[cur_insn].reason)
+ report_fail("L1 should not intercept %s when instruction is not advertised in guest CPUID",
+ insn_table[cur_insn].name);
+ else
+ report_fail("Unknown exit reason, 0x%x", exit_code);
+ }
+}
+
struct svm_test svm_tests[] = {
{ "null", default_supported, default_prepare,
default_prepare_gif_clear, null_test,
@@ -3713,6 +3787,7 @@ struct svm_test svm_tests[] = {
TEST(svm_tsc_scale_test),
TEST(pause_filter_test),
TEST(svm_shutdown_intercept_test),
+ TEST(svm_unsupported_instruction_intercept_test),
{ NULL, NULL, NULL, NULL, NULL, NULL, NULL }
};
diff --git a/x86/unittests.cfg b/x86/unittests.cfg
index 522318d32bf68..ec456d779b35c 100644
--- a/x86/unittests.cfg
+++ b/x86/unittests.cfg
@@ -253,11 +253,18 @@ arch = x86_64
[svm]
file = svm.flat
smp = 2
-test_args = "-pause_filter_test"
+test_args = "-pause_filter_test -svm_unsupported_instruction_intercept_test"
qemu_params = -cpu max,+svm -m 4g
arch = x86_64
groups = svm
+[svm_unsupported_instruction_intercept_test]
+file = svm.flat
+test_args = "svm_unsupported_instruction_intercept_test"
+qemu_params = -cpu max,+svm,-rdtscp,-xsave,-invpcid
+arch = x86_64
+groups = svm
+
[svm_pause_filter]
file = svm.flat
test_args = pause_filter_test
--
2.52.0.223.gf5cc29aaa4-goog
next prev parent reply other threads:[~2025-12-05 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 8:02 [kvm-unit-tests PATCH 0/2] x86/svm: Add testing for L1 intercept bug Kevin Cheng
2025-12-05 8:02 ` [kvm-unit-tests PATCH 1/2] x86/svm: Add missing svm intercepts Kevin Cheng
2025-12-05 8:14 ` Kevin Cheng
2025-12-05 8:02 ` Kevin Cheng [this message]
2025-12-05 8:14 ` [kvm-unit-tests PATCH] x86/svm: Add unsupported instruction intercept test Kevin Cheng
2025-12-05 8:14 ` [kvm-unit-tests PATCH 0/2] x86/svm: Add testing for L1 intercept bug Kevin Cheng
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=20251205080228.4055341-3-chengkev@google.com \
--to=chengkev@google.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=thuth@redhat.com \
--cc=yosryahmed@google.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