mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jean-Christophe Guillain" <jean-christophe@guillain.net>,
	"Paweł S" <spawel523@gmail.com>,
	"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH 0/5] KVM: Serialize vCPU creation and revert vcpu_ids tracking
Date: Mon, 21 Sep 2026 16:00:09 +0200	[thread overview]
Message-ID: <7efe2260-5c11-4e8c-812e-dd1e215ac3e4@redhat.com> (raw)
In-Reply-To: <c645070e-9829-4f98-bafc-b5d44ff2db45@leemhuis.info>

On 9/21/26 15:57, Thorsten Leemhuis wrote:
> On 9/14/26 20:12, Sean Christopherson wrote:
>> 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.
> 
> Hi Sean! Thx for handling this and sorry for pestering you, but I have
> to ask, as this fixes a regression that was already reported two times
> and introduced this cycle:
> 
> What's the plan to merge this? Is this aimed for the current or the next
> merge window? Ciao, Thorsten

For this one, but after fixing the PPC and s390 cases.  Sean, if you're 
busy I can send the v2 myself.

Paolo

>> 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.
>>
>> Patch 1 is a tangentially related bug fix; I included it 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 is must hold kvm->lock).
>>
>> Sean Christopherson (5):
>>    KVM: Reject attempts to lock all vCPUs if vCPU creation is in-progress
>>    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/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 +++++++++++------------------------
>>   4 files changed, 11 insertions(+), 40 deletions(-)
>>
>>
>> base-commit: d599822bdb66aeec5ec76297b0fc6efaaeefe07c
> 
> 


  reply	other threads:[~2026-09-21 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 18:12 Sean Christopherson
2026-09-14 18:12 ` [PATCH 1/5] KVM: Reject attempts to lock all vCPUs if vCPU creation is in-progress Sean Christopherson
2026-09-14 18:12 ` [PATCH 2/5] KVM: Protect all of kvm_vm_ioctl_create_vcpu() with kvm->lock Sean Christopherson
2026-09-14 18:12 ` [PATCH 3/5] KVM: Move check for existing vCPU ID to the top of vCPU creation Sean Christopherson
2026-09-14 18:12 ` [PATCH 4/5] Revert "KVM: Check for duplicate vcpu_id as early as possible" Sean Christopherson
2026-09-14 18:12 ` [PATCH 5/5] KVM: WARN if vCPU creation is in-progress when locking all vCPUs Sean Christopherson
2026-09-14 18:39 ` [PATCH 0/5] KVM: Serialize vCPU creation and revert vcpu_ids tracking Christian Borntraeger
2026-09-15 13:13 ` Jean-Christophe Guillain
2026-09-21 13:57 ` Thorsten Leemhuis
2026-09-21 14:00   ` Paolo Bonzini [this message]
2026-09-21 14:11     ` 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=7efe2260-5c11-4e8c-812e-dd1e215ac3e4@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jean-christophe@guillain.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=seanjc@google.com \
    --cc=spawel523@gmail.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

all inboxes | Powered by JetHome®