From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Sean Christopherson <seanjc@google.com>,
Mathias Krause <minipli@grsecurity.net>,
Andrew Jones <andrew.jones@linux.dev>
Subject: [kvm-unit-tests PATCH v3 12/20] x86/vmx: Communicate hypercalls via RAX, not a global field
Date: Thu, 14 May 2026 14:04:52 -0700 [thread overview]
Message-ID: <20260514210500.1626871-13-seanjc@google.com> (raw)
In-Reply-To: <20260514210500.1626871-1-seanjc@google.com>
Communicate hypercall requests via RAX instead of a global field. To
avoid false positives, use a larger magic value that is extremely unlikely
to be resident in RAX at the time of VMCALL (avoiding false positives is
is presumably why a global variable was used).
Using RAX instead of a shared variable ensures multi-vCPU tests won't
clobber each other's hypercalls (no such tests currently exist).
Use the "abracadabra" magic number first introduced by KVM selftests,
because if a dad joke is funny one time, it's funny every time.
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
x86/vmx.c | 32 ++++++++++++++++++++------------
x86/vmx.h | 6 ------
2 files changed, 20 insertions(+), 18 deletions(-)
diff --git a/x86/vmx.c b/x86/vmx.c
index 12e5d449..af7c4c20 100644
--- a/x86/vmx.c
+++ b/x86/vmx.c
@@ -59,7 +59,6 @@ static struct test_teardown_step teardown_steps[MAX_TEST_TEARDOWN_STEPS];
static test_guest_func v2_guest_main;
-u64 hypercall_field;
static int matched;
static int guest_finished;
@@ -1635,28 +1634,37 @@ static void test_vmx_caps(void)
"MSR_IA32_VMX_EPT_VPID_CAP");
}
+#define VMX_HYPERCALL_MAGIC 0xabacadabaULL
+
+#define HYPERCALL_MASK 0xFFF
+#define HYPERCALL_VMEXIT 0x1
+#define HYPERCALL_VMABORT 0x2
+#define HYPERCALL_VMSKIP 0x3
+
/* This function can only be called in guest */
void __attribute__((__used__)) hypercall(u32 hypercall_no)
{
- u64 val = 0;
- val = (hypercall_no & HYPERCALL_MASK) | HYPERCALL_BIT;
- hypercall_field = val;
- asm volatile("vmcall\n\t");
+ u64 val = (VMX_HYPERCALL_MAGIC << 12) | hypercall_no;
+
+ asm volatile("vmcall\n\t" : "+a"(val));
}
static bool is_hypercall(union exit_reason exit_reason)
{
+ u64 hypercall_field = this_cpu_guest_regs()->rax;
+
return exit_reason.basic == VMX_VMCALL &&
- (hypercall_field & HYPERCALL_BIT);
+ (hypercall_field >> 12) == VMX_HYPERCALL_MAGIC;
}
static int handle_hypercall(void)
{
- ulong hypercall_no;
+ struct guest_regs *regs = this_cpu_guest_regs();
+ u64 hypercall_field = regs->rax;
- hypercall_no = hypercall_field & HYPERCALL_MASK;
- hypercall_field = 0;
- switch (hypercall_no) {
+ regs->rax = 0;
+
+ switch (hypercall_field & HYPERCALL_MASK) {
case HYPERCALL_VMEXIT:
return VMX_TEST_VMEXIT;
case HYPERCALL_VMABORT:
@@ -1664,7 +1672,8 @@ static int handle_hypercall(void)
case HYPERCALL_VMSKIP:
return VMX_TEST_VMSKIP;
default:
- printf("ERROR : Invalid hypercall number : %ld\n", hypercall_no);
+ printf("ERROR : Invalid hypercall number : %ld\n",
+ hypercall_field & HYPERCALL_MASK);
}
return VMX_TEST_EXIT;
}
@@ -2060,7 +2069,6 @@ int main(int argc, const char *argv[])
int i = 0;
setup_vm();
- hypercall_field = 0;
/* We want xAPIC mode to test MMIO passthrough from L1 (us) to L2. */
smp_reset_apic();
diff --git a/x86/vmx.h b/x86/vmx.h
index c1c6eba4..098a5ef4 100644
--- a/x86/vmx.h
+++ b/x86/vmx.h
@@ -588,12 +588,6 @@ enum vm_entry_failure_code {
#define VMX_TEST_VMABORT 4
#define VMX_TEST_VMSKIP 5
-#define HYPERCALL_BIT (1ul << 12)
-#define HYPERCALL_MASK 0xFFF
-#define HYPERCALL_VMEXIT 0x1
-#define HYPERCALL_VMABORT 0x2
-#define HYPERCALL_VMSKIP 0x3
-
#define EPTP_PG_WALK_LEN_SHIFT 3ul
#define EPTP_PG_WALK_LEN_MASK 0x38ul
#define EPTP_RESERV_BITS_MASK 0x1ful
--
2.54.0.563.g4f69b47b94-goog
next prev parent reply other threads:[~2026-05-14 21:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 21:04 [kvm-unit-tests PATCH v3 00/20] x86: Better backtraces for leaf functions Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 01/20] x86/vmx: Drop unused SYSENTER "support" in nested VMX infrastructure Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 02/20] x86/vmx: Drop unused guest_regs " Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 03/20] x86/svm: Sort (and swap) GPRs by their index, not alphabetically Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 04/20] x86: Dedup guest/host context switch of registers across SVM and VMX Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 05/20] x86/virt: Use macro shenanigans to get reg offsets when swapping guest/host regs Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 06/20] x86/virt: Track "guest regs" using per-CPU variable Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 07/20] x86/svm: Don't VMLOAD/VMSAVE "guest" state around VMRUN Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 08/20] x86/vmx: Use separate VMCSes for BSP vs. AP in INIT test Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 09/20] x86/vmx: Swap GPRs after checking "launched" status Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 10/20] x86/vmx: Track VMCS "launched" state per-CPU Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 11/20] x86/vmx: Track "is this CPU in guest mode" per-CPU Sean Christopherson
2026-05-14 21:04 ` Sean Christopherson [this message]
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 13/20] x86/vmx: Initialize test stage in SIPI test *before* launching AP thread Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 14/20] x86/kvmclock: Replace spaces with tabs Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 15/20] x86/kvmclock: Skip kvmclock test when not running on KVM with CLOCKSOURCE2 Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 16/20] x86/vmx: Tag "struct vmx_msr_entry" as needing to be 16-byte aligned Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 17/20] x86/smp: Align the stack to a 16-byte boundary when invoking SMP function calls Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 18/20] x86/vmx: Write to KVM's WALL_CLOCK MSR via VM-Entry load list sync in SIPI test Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 19/20] x86: Better backtraces for leaf functions Sean Christopherson
2026-05-14 21:05 ` [kvm-unit-tests PATCH v3 20/20] x86: Prevent realmode test code instrumentation with nop-mcount 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=20260514210500.1626871-13-seanjc@google.com \
--to=seanjc@google.com \
--cc=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=minipli@grsecurity.net \
--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