From: Auger Eric <eric.auger@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v2 4/5] KVM: Kick resamplefd for split kernel irqchip
Date: Mon, 2 Mar 2020 16:07:59 +0100 [thread overview]
Message-ID: <d0b5e919-1e25-6617-86c9-50e1c12c831e@redhat.com> (raw)
In-Reply-To: <20200228161503.382656-5-peterx@redhat.com>
Hi Peter,
On 2/28/20 5:15 PM, Peter Xu wrote:
> This is majorly only for X86 because that's the only one that supports
> split irqchip for now.
>
> When the irqchip is split, we face a dilemma that KVM irqfd will be
> enabled, however the slow irqchip is still running in the userspace.
> It means that the resamplefd in the kernel irqfds won't take any
> effect and it will miss to ack INTx interrupts on EOIs.
>
> One example is split irqchip with VFIO INTx, which will break if we
> use the VFIO INTx fast path.
>
> This patch can potentially supports the VFIO fast path again for INTx,
> that the IRQ delivery will still use the fast path, while we don't
> need to trap MMIOs in QEMU for the device to emulate the EIOs (see the
> callers of vfio_eoi() hook). However the EOI of the INTx will still
> need to be done from the userspace by caching all the resamplefds in
> QEMU and kick properly for IOAPIC EOI broadcast.
>
> This is tricky because in this case the userspace ioapic irr &
> remote-irr will be bypassed. However such a change will greatly boost
> performance for assigned devices using INTx irqs (TCP_RR boosts 46%
> after this patch applied).
>
> When the userspace is responsible for the resamplefd kickup, don't
> register it on the kvm_irqfd anymore, because on newer kernels (after
> commit 654f1f13ea56, 5.2+) the KVM_IRQFD will fail if with both split
> irqchip and resamplefd. This will make sure that the fast path will
> work for all supported kernels.
>
> https://patchwork.kernel.org/patch/10738541/#22609933
>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Thanks
Eric
> ---
> accel/kvm/kvm-all.c | 85 +++++++++++++++++++++++++++++++++++++++++-
> accel/kvm/trace-events | 1 +
> hw/intc/ioapic.c | 23 +++++++++++-
> include/sysemu/kvm.h | 7 ++++
> 4 files changed, 112 insertions(+), 4 deletions(-)
>
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index d49b74512a..89771ea114 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -159,9 +159,65 @@ static const KVMCapabilityInfo kvm_required_capabilites[] = {
> static NotifierList kvm_irqchip_change_notifiers =
> NOTIFIER_LIST_INITIALIZER(kvm_irqchip_change_notifiers);
>
> +struct KVMResampleFd {
> + int gsi;
> + EventNotifier *resample_event;
> + QLIST_ENTRY(KVMResampleFd) node;
> +};
> +typedef struct KVMResampleFd KVMResampleFd;
> +
> +/*
> + * Only used with split irqchip where we need to do the resample fd
> + * kick for the kernel from userspace.
> + */
> +static QLIST_HEAD(, KVMResampleFd) kvm_resample_fd_list =
> + QLIST_HEAD_INITIALIZER(kvm_resample_fd_list);
> +
> #define kvm_slots_lock(kml) qemu_mutex_lock(&(kml)->slots_lock)
> #define kvm_slots_unlock(kml) qemu_mutex_unlock(&(kml)->slots_lock)
>
> +static inline void kvm_resample_fd_remove(int gsi)
> +{
> + KVMResampleFd *rfd;
> +
> + QLIST_FOREACH(rfd, &kvm_resample_fd_list, node) {
> + if (rfd->gsi == gsi) {
> + QLIST_REMOVE(rfd, node);
> + g_free(rfd);
> + break;
> + }
> + }
> +}
> +
> +static inline void kvm_resample_fd_insert(int gsi, EventNotifier *event)
> +{
> + KVMResampleFd *rfd = g_new0(KVMResampleFd, 1);
> +
> + rfd->gsi = gsi;
> + rfd->resample_event = event;
> +
> + QLIST_INSERT_HEAD(&kvm_resample_fd_list, rfd, node);
> +}
> +
> +bool kvm_resample_fd_notify(int gsi)
> +{
> + KVMResampleFd *rfd;
> +
> + if (!kvm_irqchip_is_split()) {
> + return false;
> + }
> +
> + QLIST_FOREACH(rfd, &kvm_resample_fd_list, node) {
> + if (rfd->gsi == gsi) {
> + event_notifier_set(rfd->resample_event);
> + trace_kvm_resample_fd_notify(gsi);
> + return true;
> + }
> + }
> +
> + return false;
> +}
> +
> int kvm_get_max_memslots(void)
> {
> KVMState *s = KVM_STATE(current_accel());
> @@ -1642,8 +1698,33 @@ static int kvm_irqchip_assign_irqfd(KVMState *s, EventNotifier *event,
> };
>
> if (rfd != -1) {
> - irqfd.flags |= KVM_IRQFD_FLAG_RESAMPLE;
> - irqfd.resamplefd = rfd;
> + assert(assign);
> + if (kvm_irqchip_is_split()) {
> + /*
> + * When the slow irqchip (e.g. IOAPIC) is in the
> + * userspace, KVM kernel resamplefd will not work because
> + * the EOI of the interrupt will be delivered to userspace
> + * instead, so the KVM kernel resamplefd kick will be
> + * skipped. The userspace here mimics what the kernel
> + * provides with resamplefd, remember the resamplefd and
> + * kick it when we receive EOI of this IRQ.
> + *
> + * This is hackery because IOAPIC is mostly bypassed
> + * (except EOI broadcasts) when irqfd is used. However
> + * this can bring much performance back for split irqchip
> + * with INTx IRQs (for VFIO, this gives 93% perf of the
> + * full fast path, which is 46% perf boost comparing to
> + * the INTx slow path).
> + */
> + kvm_resample_fd_insert(virq, resample);
> + } else {
> + irqfd.flags |= KVM_IRQFD_FLAG_RESAMPLE;
> + irqfd.resamplefd = rfd;
> + }
> + } else if (!assign) {
> + if (kvm_irqchip_is_split()) {
> + kvm_resample_fd_remove(virq);
> + }
> }
>
> if (!kvm_irqfds_enabled()) {
> diff --git a/accel/kvm/trace-events b/accel/kvm/trace-events
> index 4fb6e59d19..a68eb66534 100644
> --- a/accel/kvm/trace-events
> +++ b/accel/kvm/trace-events
> @@ -16,4 +16,5 @@ kvm_set_ioeventfd_mmio(int fd, uint64_t addr, uint32_t val, bool assign, uint32_
> kvm_set_ioeventfd_pio(int fd, uint16_t addr, uint32_t val, bool assign, uint32_t size, bool datamatch) "fd: %d @0x%x val=0x%x assign: %d size: %d match: %d"
> kvm_set_user_memory(uint32_t slot, uint32_t flags, uint64_t guest_phys_addr, uint64_t memory_size, uint64_t userspace_addr, int ret) "Slot#%d flags=0x%x gpa=0x%"PRIx64 " size=0x%"PRIx64 " ua=0x%"PRIx64 " ret=%d"
> kvm_clear_dirty_log(uint32_t slot, uint64_t start, uint32_t size) "slot#%"PRId32" start 0x%"PRIx64" size 0x%"PRIx32
> +kvm_resample_fd_notify(int gsi) "gsi %d"
>
> diff --git a/hw/intc/ioapic.c b/hw/intc/ioapic.c
> index 15747fe2c2..13921b333d 100644
> --- a/hw/intc/ioapic.c
> +++ b/hw/intc/ioapic.c
> @@ -236,8 +236,27 @@ void ioapic_eoi_broadcast(int vector)
> for (n = 0; n < IOAPIC_NUM_PINS; n++) {
> entry = s->ioredtbl[n];
>
> - if ((entry & IOAPIC_VECTOR_MASK) != vector ||
> - ((entry >> IOAPIC_LVT_TRIGGER_MODE_SHIFT) & 1) != IOAPIC_TRIGGER_LEVEL) {
> + if ((entry & IOAPIC_VECTOR_MASK) != vector) {
> + continue;
> + }
> +
> + /*
> + * When IOAPIC is in the userspace while APIC is still in
> + * the kernel (i.e., split irqchip), we have a trick to
> + * kick the resamplefd logic for registered irqfds from
> + * userspace to deactivate the IRQ. When that happens, it
> + * means the irq bypassed userspace IOAPIC (so the irr and
> + * remote-irr of the table entry should be bypassed too
> + * even if interrupt come), then we don't need to clear
> + * the remote-IRR and check irr again because they'll
> + * always be zeros.
> + */
> + if (kvm_resample_fd_notify(n)) {
> + continue;
> + }
> +
> + if (((entry >> IOAPIC_LVT_TRIGGER_MODE_SHIFT) & 1) !=
> + IOAPIC_TRIGGER_LEVEL) {
> continue;
> }
>
> diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> index 141342de98..3f0830cc4f 100644
> --- a/include/sysemu/kvm.h
> +++ b/include/sysemu/kvm.h
> @@ -555,4 +555,11 @@ int kvm_set_one_reg(CPUState *cs, uint64_t id, void *source);
> int kvm_get_one_reg(CPUState *cs, uint64_t id, void *target);
> struct ppc_radix_page_info *kvm_get_radix_page_info(void);
> int kvm_get_max_memslots(void);
> +
> +/*
> + * Notify resamplefd for EOI of specific interrupts. Returns true
> + * when one resamplefd is notified, false if no such IRQ found.
> + */
> +bool kvm_resample_fd_notify(int gsi);
> +
> #endif
>
next prev parent reply other threads:[~2020-03-02 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 16:14 [PATCH v2 0/5] vfio/pci: Fix up breakage against split irqchip and INTx Peter Xu
2020-02-28 16:14 ` [PATCH v2 1/5] vfio/pci: Disable INTx fast path if using split irqchip Peter Xu
2020-02-28 16:15 ` [PATCH v2 2/5] vfio/pci: Use kvm_irqchip_add_irqfd_notifier_gsi() for irqfds Peter Xu
2020-02-28 16:15 ` [PATCH v2 3/5] KVM: Pass EventNotifier into kvm_irqchip_assign_irqfd Peter Xu
2020-02-28 16:15 ` [PATCH v2 4/5] KVM: Kick resamplefd for split kernel irqchip Peter Xu
2020-03-02 15:07 ` Auger Eric [this message]
2020-03-05 23:58 ` Alex Williamson
2020-03-06 0:43 ` Peter Xu
2020-03-09 21:04 ` Alex Williamson
2020-03-09 22:10 ` Alex Williamson
2020-03-09 22:33 ` Alex Williamson
2020-03-10 0:38 ` Peter Xu
2020-03-10 1:54 ` Alex Williamson
2020-03-09 23:28 ` Peter Xu
2020-02-28 16:15 ` [PATCH v2 5/5] Revert "vfio/pci: Disable INTx fast path if using split irqchip" Peter Xu
2020-03-02 15:10 ` Auger Eric
2020-03-02 15:09 ` [PATCH v2 0/5] vfio/pci: Fix up breakage against split irqchip and INTx Auger Eric
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=d0b5e919-1e25-6617-86c9-50e1c12c831e@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).