Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yosry Ahmed <yosry@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 f734222792@gmail.com, Vitaly Kuznetsov <vkuznets@redhat.com>,
	 Sashiko Bot <sashiko-bot@kernel.org>
Subject: Re: [PATCH v3 12/13] KVM: selftests: Dedup assembly code for VMLAUNCH and VMRESUME
Date: Thu, 27 Aug 2026 10:17:38 -0700	[thread overview]
Message-ID: <apBxMrqEkl_7khix@google.com> (raw)
In-Reply-To: <CAO9r8zP3O_80Lr=4eKL6v-OaM9etMXPsNzADizf6ztB6YBuLHA@mail.gmail.com>

On Thu, Aug 27, 2026, Yosry Ahmed wrote:
> On Thu, Aug 27, 2026 at 9:41 AM Sean Christopherson <seanjc@google.com> wrote:
> >   #define __BUILD_VMX_VM_ENTRY_HELPER(insn, prefix, vmwrite_insn, vmwrite_operand,      \
> >                                     __host_rsp, __host_rip)                             \
> 
> The only part I really hate is vmwrite_operand. Why do we need it?  Seems
> like all the current helpers use "r", I feel like I am missing something.

...

> >   static int __##prefix##_##insn(void)                                                  \
> >   {                                                                                     \
> >         int ret;                                                                        \
> >                                                                                         \
> >         __asm__ __volatile__("push $0;"                                                 \
> >                              __stringify(vmwrite_insn) " %%rsp, %[host_rsp];"           \
> >                              "lea 1f(%%rip), %%rax;"                                    \
> >                              __stringify(vmwrite_insn) " %%rax, %[host_rip];"           \
> >                              VMX_SWITCH_GPRS_ASM                                        \
> >                              __stringify(insn)";"                                       \
> >                              "incq (%%rsp);"                                            \
> >                              "1: ;"                                                     \
> >                              VMX_SWITCH_GPRS_ASM                                        \
> >                              "pop %%rax;"                                               \
> >                              : [ret]"=&a"(ret)                                          \
> >                              : [host_rsp]__stringify(vmwrite_operand)(__host_rsp),      \
> >                                [host_rip]__stringify(vmwrite_operand)(__host_rip),      \
> >                                GUEST_REGS_OFFSETS                                       \
> >                              : "memory", "cc");                                         \
> >         return ret;                                                                     \
> >   }
> >
> >   #define BUILD_VMX_VM_ENTRY_HELPER(insn) \
> >         __BUILD_VMX_VM_ENTRY_HELPER(insn, _, vmwrite, r, (u64)HOST_RSP, (u64)HOST_RIP)  \
> >         __BUILD_VMX_VM_ENTRY_HELPER(insn, __evmcs, mov, m,                              \
> >                                     current_evmcs->host_rsp, current_evmcs->host_rip)

eVMCS is a memory operand, i.e. it's MOV RSP, [evmcs->host_rip].  The existing
evmcs_{vmresume,vmlaunch}() code is rather stupid and loads the address into a
register, and then manually encodes MOV RSP, [<reg>].

P.S. just in case you didn't already think this code is evil, the '&' in the
     above "[ret]"=&a"(ret)" is an earlyclobber that tells the compiler that
     RAX may be clobbered before all inputs and processed, i.e. prevents the
     compiler from using RAX for VMWRITE's register operand, or from using RAX
     to compute the memory operand for eVMCS's MOV.

P.P.S. even though the prototype for VMWRITE is "VMWRITE r64, r/m64", Intel is
       ass-backwards when it comes to syntax, i.e r/m64 is the source, not the
       dest, and so the field encoding *must* be a register operand.  I.e. we
       can't do something like this:

diff --git tools/testing/selftests/kvm/lib/x86/vmx.c tools/testing/selftests/kvm/lib/x86/vmx.c
index 1a8515de42b0..b5efd10950c7 100644
--- tools/testing/selftests/kvm/lib/x86/vmx.c
+++ tools/testing/selftests/kvm/lib/x86/vmx.c
@@ -179,7 +179,10 @@ void load_vmcs(struct vmx_pages *vmx)
        vmclear(vmx->shadow_vmcs_gpa);
 }
 
-#define __BUILD_VMX_VM_ENTRY_HELPER(insn, prefix, vmwrite_insn, vmwrite_operand,       \
+const u64 HOST_RSP_ENCODING = HOST_RSP;
+const u64 HOST_RIP_ENCODING = HOST_RIP;
+
+#define __BUILD_VMX_VM_ENTRY_HELPER(insn, prefix, vmwrite_insn,        \
                                    __host_rsp, __host_rip)                             \
 static int __##prefix##_##insn(void)                                                   \
 {                                                                                      \
@@ -196,16 +199,17 @@ static int __##prefix##_##insn(void)                                                      \
                             VMX_SWITCH_GPRS_ASM                                        \
                             "pop %%rax;"                                               \
                             : [ret]"=&a"(ret)                                          \
-                            : [host_rsp]__stringify(vmwrite_operand)(__host_rsp),      \
-                              [host_rip]__stringify(vmwrite_operand)(__host_rip),      \
+                            : [host_rsp]"m"(__host_rsp),                               \
+                              [host_rip]"m"(__host_rip),                               \
                               GUEST_REGS_OFFSETS                                       \
                             : "memory", "cc");                                         \
        return ret;                                                                     \
 }
 
 #define BUILD_VMX_VM_ENTRY_HELPER(insn) \
-       __BUILD_VMX_VM_ENTRY_HELPER(insn, _, vmwrite, r, (u64)HOST_RSP, (u64)HOST_RIP)  \
-       __BUILD_VMX_VM_ENTRY_HELPER(insn, __evmcs, mov, m,                              \
+       __BUILD_VMX_VM_ENTRY_HELPER(insn, _, vmwrite,                                   \
+                                   HOST_RSP_ENCODING, HOST_RIP_ENCODING)               \
+       __BUILD_VMX_VM_ENTRY_HELPER(insn, __evmcs, mov,                                 \
                                    current_evmcs->host_rsp, current_evmcs->host_rip)
 
 BUILD_VMX_VM_ENTRY_HELPER(vmlaunch)

  reply	other threads:[~2026-08-27 17:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 23:39 [PATCH v3 00/13] KVM: nVMX: Adjust VMPTRLD/VMPTRST behavior with active eVMCS Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 01/13] KVM: nVMX: Make VMPTRLD result in #UD when eVMCS is used Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 02/13] KVM: nVMX: Make VMPTRST return eVMCS GPA when it " Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 03/13] KVM: selftests: Don't clobber RFLAGS in happy path of __KVM_ASM_SAFE() Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 04/13] KVM: selftests: Adapt to the updated VMPTRST behavior when eVMCS is used Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 05/13] KVM: selftests: Check VMPTRLD with active eVMCS Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 06/13] KVM: selftests: Assert success in vmptrst(), kill off vmptrstz() Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 07/13] KVM: selftests: Always assert that vmxon() and prepare_for_vmx_operation() succeed Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 08/13] KVM: selftests: Always assert that vmclear() succeeds Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 09/13] KVM: selftests: Always assert that vmptrld() succeeds Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 10/13] KVM: selftests: Drop useless return code from load_vmcs() Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 11/13] KVM: selftests: Add macros to handle simple VMX instructions Sean Christopherson
2026-08-26 23:39 ` [PATCH v3 12/13] KVM: selftests: Dedup assembly code for VMLAUNCH and VMRESUME Sean Christopherson
2026-08-27  6:45   ` Yosry Ahmed
2026-08-27 16:40     ` Sean Christopherson
2026-08-27 16:49       ` Yosry Ahmed
2026-08-27 17:17         ` Sean Christopherson [this message]
2026-08-27 17:21           ` Yosry Ahmed
2026-08-27 17:33             ` Sean Christopherson
2026-08-27 17:50               ` Yosry Ahmed
2026-08-27 18:07                 ` Sean Christopherson
2026-08-27 18:21                   ` Yosry Ahmed
2026-08-26 23:39 ` [PATCH v3 13/13] KVM: selftests: Add and use double-underscore versions of vmlaunch() and vmresume() Sean Christopherson
2026-08-27  6:51   ` Yosry Ahmed
2026-08-27 20:28     ` Sean Christopherson
2026-08-27 20:37       ` Yosry Ahmed
2026-08-27 20:48         ` Sean Christopherson
2026-08-27 20:56           ` Yosry Ahmed
2026-08-27 21:02             ` Sean Christopherson
2026-08-27 21:05               ` Yosry Ahmed

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=apBxMrqEkl_7khix@google.com \
    --to=seanjc@google.com \
    --cc=f734222792@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sashiko-bot@kernel.org \
    --cc=vkuznets@redhat.com \
    --cc=yosry@kernel.org \
    /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