public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@linux.ibm.com>
To: Yi Wang <up2wing@gmail.com>,
	seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, wanpengli@tencent.com,
	foxywang@tencent.com, oliver.upton@linux.dev, maz@kernel.org,
	anup@brainfault.org, atishp@atishpatra.org,
	frankja@linux.ibm.com, imbrenda@linux.ibm.com,
	weijiang.yang@intel.com
Subject: Re: [v5 1/3] KVM: setup empty irq routing when create vm
Date: Fri, 17 Apr 2026 11:36:44 +0200	[thread overview]
Message-ID: <280451fd-63e9-44b0-9f56-d39dd01861b9@linux.ibm.com> (raw)
In-Reply-To: <7e958b82-4eb1-4d61-b301-dde6a19312ba@linux.ibm.com>

Am 17.04.26 um 10:19 schrieb Christian Borntraeger:
> Am 06.05.24 um 12:17 schrieb Yi Wang:
>> From: Yi Wang <foxywang@tencent.com>
>>
>> Add a new function to setup empty irq routing in kvm path, which
>> can be invoded in non-architecture-specific functions. The difference
>> compared to the kvm_setup_empty_irq_routing() is this function just
>> alloc the empty irq routing and does not need synchronize srcu, as
>> we will call it in kvm_create_vm().
>>
>> Using the new adding function, we can setup empty irq routing when
>> kvm_create_vm(), so that x86 and s390 no longer need to set
>> empty/dummy irq routing when creating an IRQCHIP 'cause it avoid
>> an synchronize_srcu.
>>
>> Signed-off-by: Yi Wang <foxywang@tencent.com>
> 
> We have recently looked into cpu consumption for virtio.
> So interestingly enough, this increases cpu consumption for things like uperf
> ping pong on s390.
> Bisect points to this commit.
> I originally thought that this is a no-op for s390, but it is not.
> 
> The reasons seems to be that nr_rt_entries is now 1 instead of 0 making every
> interrupt inject more expensive as we no longer drop out in
> 
> int kvm_irq_map_gsi(struct kvm *kvm,
>                      struct kvm_kernel_irq_routing_entry *entries, int gsi)
> {
>          struct kvm_irq_routing_table *irq_rt;
>          struct kvm_kernel_irq_routing_entry *e;
>          int n = 0;
> 
>          irq_rt = srcu_dereference_check(kvm->irq_routing, &kvm->irq_srcu,
>                                          lockdep_is_held(&kvm->irq_lock));
>          if (irq_rt && gsi < irq_rt->nr_rt_entries) {  <---------
> 
Hmm, I guess I misread the code and the problem is likely not this.
Let me have another look.

  reply	other threads:[~2026-04-17  9:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 10:17 [v5 0/3] KVM: irqchip: synchronize srcu only if needed Yi Wang
2024-05-06 10:17 ` [v5 1/3] KVM: setup empty irq routing when create vm Yi Wang
2024-05-06 11:41   ` Christian Borntraeger
2026-04-17  8:19   ` Christian Borntraeger
2026-04-17  9:36     ` Christian Borntraeger [this message]
2026-04-17 10:19       ` Paolo Bonzini
2026-04-17 10:26         ` Christian Borntraeger
2024-05-06 10:17 ` [v5 2/3] KVM: x86: don't setup empty irq routing when KVM_CAP_SPLIT_IRQCHIP Yi Wang
2024-06-11  0:25   ` Sean Christopherson
2024-06-11  1:54     ` Yi Wang
2024-05-06 10:17 ` [v5 3/3] KVM: s390: don't setup dummy routing when KVM_CREATE_IRQCHIP Yi Wang
2024-05-06 11:42   ` Christian Borntraeger
2024-06-10 16:19   ` Sean Christopherson
2024-06-11 11:53     ` Christian Borntraeger
2024-06-12  1:18 ` [v5 0/3] KVM: irqchip: synchronize srcu only if needed Sean Christopherson
2024-06-12 13:16   ` Yi Wang

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=280451fd-63e9-44b0-9f56-d39dd01861b9@linux.ibm.com \
    --to=borntraeger@linux.ibm.com \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=foxywang@tencent.com \
    --cc=frankja@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=up2wing@gmail.com \
    --cc=wanpengli@tencent.com \
    --cc=weijiang.yang@intel.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