From: Sean Christopherson <seanjc@google.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Anup Patel <anup@brainfault.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kiryl Shutsemau <kas@kernel.org>,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
"Atish Patra" <atish.patra@linux.dev>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org,
x86@kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org,
"Jean-Christophe Guillain" <jean-christophe@guillain.net>,
"Paweł S" <spawel523@gmail.com>
Subject: [PATCH v2 0/7] KVM: Serialize vCPU creation and revert vcpu_ids tracking
Date: Mon, 21 Sep 2026 10:44:38 -0700 [thread overview]
Message-ID: <20260921174445.911676-1-seanjc@google.com> (raw)
Serialize vCPU creation by holding kvm->lock for the entirety of
kvm_vm_ioctl_create_vcpu(), and then revert the now-redundant tracking adding
by commit 97d65b544f48 ("KVM: Check for duplicate vcpu_id as early as
possible"). I botched the math when justifying the vcpu_ids tracking; it's not
an extra 256 bytes, it's an extra 2048 bytes. Roughly doubling the size of
"struct kvm" tripped x86's KVM_SANITY_CHECK_VM_STRUCT_SIZE, and obviously isn't
something we want to do in general.
The TL;DR of why it's a-ok to serialize vCPU creation is that no VMM actually
does parallel vCPU creation. As with so many things, KVM's current behavior is
the result of decades-old cruft, not intentional, deliberate design.
Patches 1-3 are a tangentially related cleanups and bug fixes; I included them
here because holding kvm->lock for all of vCPU creation allows WARNing if KVM
attempts to lock all vCPUs if vCPU creation is in-progress (the caller must
hold kvm->lock).
v2:
- Tweak patch 1's changelog to clarify that that only x86's manual checks are
dropped. [Sashiko]
- Add patches to convert additional arm64 and RISC-V usage to
kvm_is_vcpu_creation_in_progress(). [Sashiko]
- Remove acquisition of kvm->lock from s390 and PPC vCPU creation flows.
[Christian, Sashiko]
- Add Jean-Christophe's Tested-by to the revert.
v1: https://lore.kernel.org/all/20260914181223.289061-1-seanjc@google.com
Sean Christopherson (7):
KVM: Reject attempts to lock all vCPUs if vCPU creation is in-progress
KVM: arm64: vgic: Rely on vCPU creation check in "trylock all vCPUs"
KVM: RISC-V: Use kvm_is_vcpu_creation_in_progress() instead of
open-coded equivalent
KVM: Protect all of kvm_vm_ioctl_create_vcpu() with kvm->lock
KVM: Move check for existing vCPU ID to the top of vCPU creation
Revert "KVM: Check for duplicate vcpu_id as early as possible"
KVM: WARN if vCPU creation is in-progress when locking all vCPUs
arch/arm64/kvm/vgic/vgic-init.c | 12 ++++-------
arch/powerpc/kvm/book3s_hv.c | 2 --
arch/riscv/kvm/aia_device.c | 2 +-
arch/s390/kvm/s390/s390.c | 5 +----
arch/x86/kvm/svm/sev.c | 10 ----------
arch/x86/kvm/vmx/tdx.c | 5 -----
include/linux/kvm_host.h | 1 -
virt/kvm/kvm_main.c | 35 +++++++++++----------------------
8 files changed, 17 insertions(+), 55 deletions(-)
base-commit: d599822bdb66aeec5ec76297b0fc6efaaeefe07c
--
2.55.0.1082.g2b9226bbc0-goog
next reply other threads:[~2026-09-21 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 17:44 Sean Christopherson [this message]
2026-09-21 17:44 ` [PATCH v2 1/7] KVM: Reject attempts to lock all vCPUs if vCPU creation is in-progress Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 2/7] KVM: arm64: vgic: Rely on vCPU creation check in "trylock all vCPUs" Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 3/7] KVM: RISC-V: Use kvm_is_vcpu_creation_in_progress() instead of open-coded equivalent Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 4/7] KVM: Protect all of kvm_vm_ioctl_create_vcpu() with kvm->lock Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 5/7] KVM: Move check for existing vCPU ID to the top of vCPU creation Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 6/7] Revert "KVM: Check for duplicate vcpu_id as early as possible" Sean Christopherson
2026-09-21 17:44 ` [PATCH v2 7/7] KVM: WARN if vCPU creation is in-progress when locking all vCPUs Sean Christopherson
2026-09-22 8:06 ` [PATCH v2 0/7] KVM: Serialize vCPU creation and revert vcpu_ids tracking Jean-Christophe Guillain
2026-09-22 19:15 ` Naveen N Rao
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=20260921174445.911676-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=jean-christophe@guillain.net \
--cc=kas@kernel.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=spawel523@gmail.com \
--cc=x86@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
all inboxes | Powered by JetHome®