From: Auger Eric <eric.auger@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v1.1 4/5] KVM: Kick resamplefd for split kernel irqchip
Date: Fri, 28 Feb 2020 11:36:05 +0100 [thread overview]
Message-ID: <7851fc72-6001-25d3-8b17-f6fda827ea74@redhat.com> (raw)
In-Reply-To: <8c3e3f25-b20e-08bd-fa1e-f307fe7f02a4@redhat.com>
Hi Paolo,
On 2/28/20 11:34 AM, Paolo Bonzini wrote:
> On 27/02/20 22:14, Auger Eric wrote:
>>> Yes KVM kernel side should not be involed when we're using split
>>> irqchip in this case. However it should still belongs to the work of
>>> the userspace KVM module (kvm-all.c) so that it can still "mimic" the
>>> resamplefd feature that KVM_IRQFD provides.
>> OK. So that what my actual question. Should this be handled by kvm-all.c?
>
> I think it should; kvm-all.c in this case is providing the API to enable
> irqfds (including resamplefds).
>
> You could have a generic file descriptor<->interrupt routing subsystem,
> but for now that only exists for KVM so that's where Peter's code need
> to go.
OK
Thanks
Eric
>
> Paolo
>
next prev parent reply other threads:[~2020-02-28 10:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 22:50 [PATCH 0/5] vfio/pci: Fix up breakage against split irqchip and INTx Peter Xu
2020-02-26 22:50 ` [PATCH 1/5] vfio/pci: Disable INTx fast path if using split irqchip Peter Xu
2020-02-27 16:53 ` Auger Eric
2020-02-27 17:10 ` Peter Xu
2020-02-26 22:50 ` [PATCH 2/5] vfio/pci: Use kvm_irqchip_add_irqfd_notifier_gsi() for irqfds Peter Xu
2020-02-27 11:04 ` Auger Eric
2020-02-27 16:41 ` Cornelia Huck
2020-02-26 22:54 ` [PATCH 3/5] KVM: Pass EventNotifier into kvm_irqchip_assign_irqfd Peter Xu
2020-02-27 17:01 ` Auger Eric
2020-02-26 22:55 ` [PATCH 4/5] KVM: Kick resamplefd for split kernel irqchip Peter Xu
2020-02-27 17:00 ` [PATCH v1.1 " Peter Xu
2020-02-27 17:18 ` Peter Xu
2020-02-27 17:42 ` Auger Eric
2020-02-27 18:00 ` Peter Xu
2020-02-27 18:22 ` Auger Eric
2020-02-27 19:19 ` Peter Xu
2020-02-27 21:14 ` Auger Eric
2020-02-27 21:52 ` Peter Xu
2020-02-28 10:34 ` Paolo Bonzini
2020-02-28 10:36 ` Auger Eric [this message]
2020-02-28 10:34 ` [PATCH " Paolo Bonzini
2020-02-28 14:58 ` Peter Xu
2020-02-28 15:24 ` Paolo Bonzini
2020-02-26 22:55 ` [PATCH 5/5] Revert "vfio/pci: Disable INTx fast path if using split irqchip" Peter Xu
2020-02-27 15:32 ` [PATCH 0/5] vfio/pci: Fix up breakage against split irqchip and INTx Auger Eric
2020-02-27 15:51 ` Peter Xu
2020-02-27 17:02 ` Peter Xu
2020-02-28 10:36 ` Paolo Bonzini
2020-02-28 15:25 ` Peter Xu
2020-02-28 15:32 ` 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=7851fc72-6001-25d3-8b17-f6fda827ea74@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).