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
Subject: Re: [PATCH v3 06/10] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK
Date: Fri, 24 Jul 2026 08:37:35 -0700 [thread overview]
Message-ID: <amOGv2t9l9DpoW2a@google.com> (raw)
In-Reply-To: <20260629183746.699840-7-yosry@kernel.org>
On Mon, Jun 29, 2026, Yosry Ahmed wrote:
> Now that nVMX test codes preserves GPRs across nested VM-Exits
> (specifically RBP, RDX, and RDI among others), drop the ucall-specific
> hack to avoid clobbering these registers.
>
> Assisted-by: Gemini:gemini-3.1-pro
Did Gemini really help you write this patch? It's ok if it did, I just want to
be precise with documenting how AI was used so that when I get a patch that was
indeed heavily helped by AI, I can actually key off the "AI was used" information
for context when reviewing.
> Signed-off-by: Yosry Ahmed <yosry@kernel.org>
> ---
> tools/testing/selftests/kvm/lib/x86/ucall.c | 32 ++-------------------
> 1 file changed, 2 insertions(+), 30 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/lib/x86/ucall.c b/tools/testing/selftests/kvm/lib/x86/ucall.c
> index e7dd5791959ba..38050c60a0670 100644
> --- a/tools/testing/selftests/kvm/lib/x86/ucall.c
> +++ b/tools/testing/selftests/kvm/lib/x86/ucall.c
> @@ -10,36 +10,8 @@
>
> void ucall_arch_do_ucall(gva_t uc)
> {
> - /*
> - * FIXME: Revert this hack (the entire commit that added it) once nVMX
> - * preserves L2 GPRs across a nested VM-Exit. If a ucall from L2, e.g.
> - * to do a GUEST_SYNC(), lands the vCPU in L1, any and all GPRs can be
> - * clobbered by L1. Save and restore non-volatile GPRs (clobbering RBP
> - * in particular is problematic) along with RDX and RDI (which are
> - * inputs), and clobber volatile GPRs. *sigh*
> - */
> -#define HORRIFIC_L2_UCALL_CLOBBER_HACK \
> - "rcx", "rsi", "r8", "r9", "r10", "r11"
> -
> - asm volatile("push %%rbp\n\t"
> - "push %%r15\n\t"
> - "push %%r14\n\t"
> - "push %%r13\n\t"
> - "push %%r12\n\t"
> - "push %%rbx\n\t"
> - "push %%rdx\n\t"
> - "push %%rdi\n\t"
> - "in %[port], %%al\n\t"
> - "pop %%rdi\n\t"
> - "pop %%rdx\n\t"
> - "pop %%rbx\n\t"
> - "pop %%r12\n\t"
> - "pop %%r13\n\t"
> - "pop %%r14\n\t"
> - "pop %%r15\n\t"
> - "pop %%rbp\n\t"
> - : : [port] "d" (UCALL_PIO_PORT), "D" (uc) : "rax", "memory",
> - HORRIFIC_L2_UCALL_CLOBBER_HACK);
> + asm volatile("in %[port], %%al"
> + : : [port] "d" (UCALL_PIO_PORT), "D" (uc) : "rax", "memory");
> }
>
> void *ucall_arch_get_ucall(struct kvm_vcpu *vcpu)
> --
> 2.55.0.rc0.799.gd6f94ed593-goog
>
next prev parent reply other threads:[~2026-07-24 15:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 18:37 [PATCH v3 00/10] KVM: selftests: Stress save+restore and #PF (ft. nested) Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 01/10] KVM: selftests: Move STR() and XSTR() definitions to test_util.h Yosry Ahmed
2026-07-24 15:26 ` Sean Christopherson
2026-06-29 18:37 ` [PATCH v3 02/10] KVM: selftests: Fix RAX and RFLAGS VMCB offsets when running L2 Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 03/10] KVM: selftests: Use an array for guest_regs (and fix offsets) Yosry Ahmed
2026-07-24 15:33 ` Sean Christopherson
2026-07-24 16:18 ` Yosry Ahmed
2026-07-24 17:03 ` Sean Christopherson
2026-07-24 17:44 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 04/10] KVM: selftests: Move GPR load/save definitions outside of nSVM code Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 05/10] KVM: selftests: Reuse GPR switching logic for nVMX Yosry Ahmed
2026-06-29 18:49 ` sashiko-bot
2026-06-29 20:26 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 06/10] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK Yosry Ahmed
2026-07-24 15:37 ` Sean Christopherson [this message]
2026-07-24 16:20 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 07/10] KVM: selftests: Add basic stress test for save+restore and #PF handling Yosry Ahmed
2026-07-24 16:45 ` Sean Christopherson
2026-07-24 17:38 ` Yosry Ahmed
2026-07-24 18:12 ` Sean Christopherson
2026-07-24 18:25 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 08/10] KVM: selftests: Trigger save+restore randomly in the #PF stress test Yosry Ahmed
2026-06-29 18:48 ` sashiko-bot
2026-06-29 20:29 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 09/10] KVM: selftests: Support running stress save+restore and #PF test in L2 Yosry Ahmed
2026-07-24 17:37 ` Sean Christopherson
2026-07-24 17:40 ` Yosry Ahmed
2026-06-29 18:37 ` [PATCH v3 10/10] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test Yosry Ahmed
2026-07-24 17:50 ` Sean Christopherson
2026-07-24 18:15 ` Yosry Ahmed
2026-07-24 18:25 ` Sean Christopherson
2026-07-24 18:35 ` Yosry Ahmed
2026-07-24 20:32 ` 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=amOGv2t9l9DpoW2a@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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