From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
Date: Mon, 21 May 2012 14:35:42 +0300 [thread overview]
Message-ID: <4FBA288E.9000208@redhat.com> (raw)
In-Reply-To: <4FBA2784.8010605@siemens.com>
On 05/21/2012 02:31 PM, Jan Kiszka wrote:
> On 2012-05-20 11:45, Avi Kivity wrote:
> > On 05/20/2012 05:42 PM, Michael S. Tsirkin wrote:
> >> On Thu, May 17, 2012 at 10:32:28AM -0300, Jan Kiszka wrote:
> >>> After this series, to only reasons to still use qemu-kvm for production
> >>> purposes will be PCI device assignment
> >>
> >> Yay!
> >>
> >> By the way, there are probably not many reasons to keep the
> >> assignment code out of qemu.git. It duplicates a ton of
> >> code from core pci, but that's easier to fix in-tree
> >> than out of tree.
> >
> > Right. And Jan, if you want to push device assignment to qemu.git,
> > please update it in qemu-kvm.git instead of rewriting it in qemu.git.
> >
>
> That's precisely my plan. The conversion of pci-assign to the new APIs
> is too hairy to combine it with a refactoring and upstream push. But
> this depends on this series being merged back into qemu-kvm first.
I'll try to expedite this.
> This and also the previous MSI work will cause some merge conflicts.
> Once upsteam accepted these series, I will provide the usual merge work
> as pull request.
Thanks in advance.
> There are also some other "smaller" pieces to prepare for device
> assignment (e.g. PCI IRQ routing hooks, full PCI address properties)
> that I'm preparing for upstream. Will send some of them later.
Okay - looking forward to that.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
Date: Mon, 21 May 2012 14:35:42 +0300 [thread overview]
Message-ID: <4FBA288E.9000208@redhat.com> (raw)
In-Reply-To: <4FBA2784.8010605@siemens.com>
On 05/21/2012 02:31 PM, Jan Kiszka wrote:
> On 2012-05-20 11:45, Avi Kivity wrote:
> > On 05/20/2012 05:42 PM, Michael S. Tsirkin wrote:
> >> On Thu, May 17, 2012 at 10:32:28AM -0300, Jan Kiszka wrote:
> >>> After this series, to only reasons to still use qemu-kvm for production
> >>> purposes will be PCI device assignment
> >>
> >> Yay!
> >>
> >> By the way, there are probably not many reasons to keep the
> >> assignment code out of qemu.git. It duplicates a ton of
> >> code from core pci, but that's easier to fix in-tree
> >> than out of tree.
> >
> > Right. And Jan, if you want to push device assignment to qemu.git,
> > please update it in qemu-kvm.git instead of rewriting it in qemu.git.
> >
>
> That's precisely my plan. The conversion of pci-assign to the new APIs
> is too hairy to combine it with a refactoring and upstream push. But
> this depends on this series being merged back into qemu-kvm first.
I'll try to expedite this.
> This and also the previous MSI work will cause some merge conflicts.
> Once upsteam accepted these series, I will provide the usual merge work
> as pull request.
Thanks in advance.
> There are also some other "smaller" pieces to prepare for device
> assignment (e.g. PCI IRQ routing hooks, full PCI address properties)
> that I'm preparing for upstream. Will send some of them later.
Okay - looking forward to that.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-21 11:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 13:32 [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 01/11] msix: Factor out msix_get_message Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 02/11] msix: Invoke msix_handle_mask_update on msix_mask_all Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 03/11] msix: Introduce vector notifiers Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 04/11] kvm: Rename kvm_irqchip_add_route to kvm_irqchip_add_irq_route Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 05/11] kvm: Introduce kvm_irqchip_add_msi_route Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 06/11] kvm: Publicize kvm_irqchip_release_virq Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 07/11] kvm: Make kvm_irqchip_commit_routes an internal service Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 08/11] kvm: Introduce kvm_irqchip_add/remove_irqfd Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 09/11] kvm: Enable use of kvm_irqchip_in_kernel in hwlib code Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 10/11] msix: Add msix_nr_vectors_allocated Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-17 13:32 ` [RFC][PATCH v2 11/11] virtio/vhost: Add support for KVM in-kernel MSI injection Jan Kiszka
2012-05-17 13:32 ` [Qemu-devel] " Jan Kiszka
2012-05-20 14:20 ` [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost Avi Kivity
2012-05-20 14:20 ` [Qemu-devel] " Avi Kivity
2012-05-20 14:42 ` Michael S. Tsirkin
2012-05-20 14:42 ` [Qemu-devel] " Michael S. Tsirkin
2012-05-20 14:45 ` Avi Kivity
2012-05-20 14:45 ` [Qemu-devel] " Avi Kivity
2012-05-21 11:31 ` Jan Kiszka
2012-05-21 11:31 ` [Qemu-devel] " Jan Kiszka
2012-05-21 11:35 ` Avi Kivity [this message]
2012-05-21 11:35 ` Avi Kivity
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=4FBA288E.9000208@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.