LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Longpeng (Mike, Cloud Infrastructure Service Product Dept.)" <longpeng2@huawei.com>
To: <pbonzini@redhat.com>
Cc: <seanjc@google.com>, <vkuznets@redhat.com>,
<wanpengli@tencent.com>, <jmattson@google.com>, <joro@8bytes.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<hpa@zytor.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <arei.gonglei@huawei.com>
Subject: Re: [PATCH] kvm: irqfd: avoid update unmodified entries of the routing
Date: Fri, 10 Sep 2021 15:43:22 +0800 [thread overview]
Message-ID: <8bae4a6d-9b89-2543-fbed-7deb1d75fc41@huawei.com> (raw)
In-Reply-To: <20210827080003.2689-1-longpeng2@huawei.com>
Hi guys,
Do you have any suggestions ? Thanks.
在 2021/8/27 16:00, Longpeng(Mike) 写道:
> All of the irqfds would to be updated when update the irq
> routing, it's too expensive if there're too many irqfds.
>
> However we can reduce the cost by avoid some unnecessary
> updates. For irqs of MSI type on X86, the update can be
> saved if the msi values are not change.
>
> The vfio migration could receives benefit from this optimi-
> zaiton. The test VM has 128 vcpus and 8 VF (with 65 vectors
> enabled), so the VM has more than 520 irqfds. We mesure the
> cost of the vfio_msix_enable (in QEMU, it would set routing
> for each irqfd) for each VF, and we can see the total cost
> can be significantly reduced.
>
> Origin Apply this Patch
> 1st 8 4
> 2nd 15 5
> 3rd 22 6
> 4th 24 6
> 5th 36 7
> 6th 44 7
> 7th 51 8
> 8th 58 8
> Total 258ms 51ms
>
> We're also tring to optimize the QEMU part [1], but it's still
> worth to optimize the KVM to gain more benefits.
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg04215.html
>
> Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
> ---
> arch/x86/kvm/x86.c | 9 +++++++++
> include/linux/kvm_host.h | 2 ++
> virt/kvm/eventfd.c | 15 ++++++++++++++-
> 3 files changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index e5d5c5e..22cf20e 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -12023,6 +12023,15 @@ int kvm_arch_update_irqfd_routing(struct kvm *kvm, unsigned int host_irq,
> return static_call(kvm_x86_update_pi_irte)(kvm, host_irq, guest_irq, set);
> }
>
> +bool kvm_arch_irqfd_route_changed(struct kvm_kernel_irq_routing_entry *old,
> + struct kvm_kernel_irq_routing_entry *new)
> +{
> + if (new->type != KVM_IRQ_ROUTING_MSI)
> + return true;
> +
> + return !!memcmp(&old->msi, &new->msi, sizeof(new->msi));
> +}
> +
> bool kvm_vector_hashing_enabled(void)
> {
> return vector_hashing;
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index ae7735b..c0954ae 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -1621,6 +1621,8 @@ void kvm_arch_irq_bypass_del_producer(struct irq_bypass_consumer *,
> void kvm_arch_irq_bypass_start(struct irq_bypass_consumer *);
> int kvm_arch_update_irqfd_routing(struct kvm *kvm, unsigned int host_irq,
> uint32_t guest_irq, bool set);
> +bool kvm_arch_irqfd_route_changed(struct kvm_kernel_irq_routing_entry *,
> + struct kvm_kernel_irq_routing_entry *);
> #endif /* CONFIG_HAVE_KVM_IRQ_BYPASS */
>
> #ifdef CONFIG_HAVE_KVM_INVALID_WAKEUPS
> diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
> index e996989..2ad013b 100644
> --- a/virt/kvm/eventfd.c
> +++ b/virt/kvm/eventfd.c
> @@ -281,6 +281,13 @@ int __attribute__((weak)) kvm_arch_update_irqfd_routing(
> {
> return 0;
> }
> +
> +bool __attribute__((weak)) kvm_arch_irqfd_route_changed(
> + struct kvm_kernel_irq_routing_entry *old,
> + struct kvm_kernel_irq_routing_entry *new)
> +{
> + return true;
> +}
> #endif
>
> static int
> @@ -615,10 +622,16 @@ void kvm_irq_routing_update(struct kvm *kvm)
> spin_lock_irq(&kvm->irqfds.lock);
>
> list_for_each_entry(irqfd, &kvm->irqfds.items, list) {
> +#ifdef CONFIG_HAVE_KVM_IRQ_BYPASS
> + /* Under irqfds.lock, so can read irq_entry safely */
> + struct kvm_kernel_irq_routing_entry old = irqfd->irq_entry;
> +#endif
> +
> irqfd_update(kvm, irqfd);
>
> #ifdef CONFIG_HAVE_KVM_IRQ_BYPASS
> - if (irqfd->producer) {
> + if (irqfd->producer &&
> + kvm_arch_irqfd_route_changed(&old, &irqfd->irq_entry)) {
> int ret = kvm_arch_update_irqfd_routing(
> irqfd->kvm, irqfd->producer->irq,
> irqfd->gsi, 1);
>
next prev parent reply other threads:[~2021-09-10 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 8:00 [PATCH] kvm: irqfd: avoid update unmodified entries of the routing Longpeng(Mike)
2021-09-10 7:43 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.) [this message]
2021-09-23 16:34 ` Paolo Bonzini
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=8bae4a6d-9b89-2543-fbed-7deb1d75fc41@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).