From: sashiko-bot@kernel.org
To: "Yosry Ahmed" <yosry@kernel.org>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v5 05/13] KVM: selftests: Reuse GPR switching logic for nVMX
Date: Tue, 28 Jul 2026 17:54:56 +0000 [thread overview]
Message-ID: <20260728175456.67E991F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728174232.2423257-6-yosry@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The newly introduced VMX_SWITCH_GPRS_ASM macro uses a shared global variable `guest_regs` for swapping host and guest general-purpose registers, introducing a race condition when multiple vCPUs execute nested VMX instructions concurrently.
--
--- Patch [5]: [PATCH v5 05/13] KVM: selftests: Reuse GPR switching logic for nVMX ---
commit a0021d28e505a4c708c955c20d96663fad9fc879
Author: Yosry Ahmed <yosry@kernel.org>
KVM: selftests: Reuse GPR switching logic for nVMX
This commit reuses the SVM GPR switching logic for nVMX by defining
VMX_SWITCH_GPRS_ASM. It replaces the previous push/pop sequence with
macro calls that swap a broader set of registers using GUEST_SWITCH_GPR_ASM.
> diff --git a/tools/testing/selftests/kvm/include/x86/vmx.h b/tools/testing/selftests/kvm/include/x86/vmx.h
> --- a/tools/testing/selftests/kvm/include/x86/vmx.h
> +++ b/tools/testing/selftests/kvm/include/x86/vmx.h
> @@ -290,6 +290,23 @@ struct vmx_msr_entry {
> u64 value;
> } __attribute__ ((aligned(16)));
>
> +#define VMX_SWITCH_GPRS_ASM \
> + GUEST_SWITCH_GPR_ASM(rax) \
> + GUEST_SWITCH_GPR_ASM(rbx) \
[Severity: Medium]
Since GUEST_SWITCH_GPR_ASM() uses the global guest_regs structure, will this
cause a data race when multiple vCPUs execute nested VMX instructions
concurrently?
When vmlaunch or vmresume is executed concurrently by multiple threads (such
as in the memstress test), they might race to read and write to this shared
variable, potentially corrupting host callee-saved registers like rbx or r12.
Could this lead to host test code crashes when one vCPU restores another
vCPU's parked host registers?
> + GUEST_SWITCH_GPR_ASM(rcx) \
> + GUEST_SWITCH_GPR_ASM(rdx) \
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728174232.2423257-1-yosry@kernel.org?part=5
next prev parent reply other threads:[~2026-07-28 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 17:42 [PATCH v5 00/13] KVM: selftests: Stress save+restore and #PF (ft. nested) Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 01/13] KVM: selftests: Use __stringify() instead of custom XSTR() macros Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 02/13] KVM: selftests: Fix RAX and RFLAGS VMCB offsets when running L2 Yosry Ahmed
2026-07-28 17:55 ` sashiko-bot
2026-07-28 17:42 ` [PATCH v5 03/13] KVM: selftests: Rework GPR registers switching for SVM (and fix offsets) Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 04/13] KVM: selftests: Handle rflags save/restore for SVM in guest_regs Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 05/13] KVM: selftests: Reuse GPR switching logic for nVMX Yosry Ahmed
2026-07-28 17:54 ` sashiko-bot [this message]
2026-07-28 17:42 ` [PATCH v5 06/13] KVM: selftests: Drop HORRIFIC_L2_UCALL_CLOBBER_HACK Yosry Ahmed
2026-07-28 17:55 ` sashiko-bot
2026-07-28 17:42 ` [PATCH v5 07/13] KVM: selftests: Add a blank line before logging assertion failures Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 08/13] KVM: selftests: Expose PTE masks to guests as part of an MMU Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 09/13] KVM: selftests: Do not intercept #PF by default in nVMX tests Yosry Ahmed
2026-07-28 17:45 ` Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 10/13] KVM: selftests: Add basic stress test for save+restore and #PF handling Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 11/13] KVM: selftests: Trigger save+restore randomly in the #PF stress test Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 12/13] KVM: selftests: Support running stress save+restore and #PF test in L2 Yosry Ahmed
2026-07-28 17:42 ` [PATCH v5 13/13] KVM: selftests: Trigger L2->L1 exits stress save+restore and #PF test 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=20260728175456.67E991F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.