From: "Longpeng(Mike)" via <qemu-devel@nongnu.org>
To: <mst@redhat.com>, <jasowang@redhat.com>, <pbonzini@redhat.com>
Cc: <arei.gonglei@huawei.com>, <yechuan@huawei.com>,
<eperezma@redhat.com>, <alex.williamson@redhat.com>,
<mtosatti@redhat.com>, <clg@redhat.com>, <qemu-devel@nongnu.org>,
Longpeng <longpeng2@huawei.com>
Subject: [PATCH v1 0/3] virtio-pci: optimize set_guest_notifier
Date: Tue, 28 Feb 2023 17:39:34 +0800 [thread overview]
Message-ID: <20230228093937.2515-1-longpeng2@huawei.com> (raw)
From: Longpeng <longpeng2@huawei.com>
This patchset optimizes the time-consuming operation in virtio_pci_set_guest_notifier,
especially for the vhost-vdpa migration, the time spend on set_guest_notifier can
reduce 87% in some cases.
Longpeng (Mike) (3):
virtio-pci: submit msi route changes in batch
kvm-irqchip: use KVMRouteChange API to update msi route
virtio-pci: defer to commit kvm irq routing when enable msi/msix
accel/kvm/kvm-all.c | 10 +--
accel/stubs/kvm-stub.c | 2 +-
hw/intc/ioapic.c | 5 +-
hw/misc/ivshmem.c | 6 +-
hw/vfio/pci.c | 5 +-
hw/virtio/virtio-pci.c | 140 ++++++++++++++++++++++++++++++++-----
include/hw/virtio/virtio.h | 1 +
include/sysemu/kvm.h | 2 +-
target/i386/kvm/kvm.c | 6 +-
9 files changed, 145 insertions(+), 32 deletions(-)
--
2.23.0
next reply other threads:[~2023-02-28 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:39 Longpeng(Mike) via [this message]
2023-02-28 9:39 ` [PATCH v1 1/3] virtio-pci: submit msi route changes in batch Longpeng(Mike) via
2023-02-28 10:17 ` Michael S. Tsirkin
2023-02-28 11:20 ` longpeng2--- via
2023-02-28 11:39 ` longpeng2--- via
2023-02-28 12:09 ` Michael S. Tsirkin
2023-02-28 10:18 ` Michael S. Tsirkin
2023-02-28 11:24 ` longpeng2--- via
2023-02-28 9:39 ` [PATCH v1 2/3] kvm-irqchip: use KVMRouteChange API to update msi route Longpeng(Mike) via
2023-02-28 9:39 ` [PATCH v1 3/3] virtio-pci: defer to commit kvm irq routing when enable msi/msix Longpeng(Mike) via
2023-02-28 10:40 ` Michael S. Tsirkin
2023-02-28 11:07 ` Daniel P. Berrangé
2023-02-28 12:29 ` Michael S. Tsirkin
2023-02-28 13:05 ` Daniel P. Berrangé
2023-02-28 11:10 ` longpeng2--- via
2023-02-28 11:36 ` Michael S. Tsirkin
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=20230228093937.2515-1-longpeng2@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=alex.williamson@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=clg@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=longpeng2@huawei.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=yechuan@huawei.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).