All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
Date: Sun, 20 May 2012 17:20:22 +0300	[thread overview]
Message-ID: <4FB8FDA6.3070001@redhat.com> (raw)
In-Reply-To: <cover.1337261556.git.jan.kiszka@web.de>

On 05/17/2012 04:32 PM, Jan Kiszka wrote:
> [ changes in v2: rebase over uq/master ]
>
> This series is another major milestone of merging qemu-kvm into
> upstream. It implements the required interfaces and logic to directly
> inject MSI-X interrupts generated by the vhost-net kernel module into
> the KVM in-kernel irqchip. This involves
>  - establishing MSI vector notifiers, so far triggered on relevant MSI-X
>    configuration changes of subscribed PCI devices
>  - support for static vIRQ-to-MSI routes
>  - an API for linking an IRQFD with such a vIRQ
>  - the usage of these services in virtio-pci to enable direct injection
>
> The series also contains some smaller refactorings of the KVM IRQ
> routing API such as automatic committing of route changes. It applies on
> top of the KVM MSI support series [1] posted recently. The complete
> stack is available at
>
>     git://git.kiszka.org/qemu-kvm.git queues/kvm-msi-irqfd
>
> If the proposes API is acceptable, I will also provide some morphing
> patches for qemu-kvm to make the merge of both trees smoother.
>
> After this series, to only reasons to still use qemu-kvm for production
> purposes will be PCI device assignment and potential dependencies on
> legacy command line switches as well as vmstate formats (when requiring
> backward migration support). However, the majority of users should be
> able to switch to upstream QEMU seamlessly and finally receive the same
> level of performance on x86.
>
>

Thanks, applied.

-- 
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@web.de>
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: Sun, 20 May 2012 17:20:22 +0300	[thread overview]
Message-ID: <4FB8FDA6.3070001@redhat.com> (raw)
In-Reply-To: <cover.1337261556.git.jan.kiszka@web.de>

On 05/17/2012 04:32 PM, Jan Kiszka wrote:
> [ changes in v2: rebase over uq/master ]
>
> This series is another major milestone of merging qemu-kvm into
> upstream. It implements the required interfaces and logic to directly
> inject MSI-X interrupts generated by the vhost-net kernel module into
> the KVM in-kernel irqchip. This involves
>  - establishing MSI vector notifiers, so far triggered on relevant MSI-X
>    configuration changes of subscribed PCI devices
>  - support for static vIRQ-to-MSI routes
>  - an API for linking an IRQFD with such a vIRQ
>  - the usage of these services in virtio-pci to enable direct injection
>
> The series also contains some smaller refactorings of the KVM IRQ
> routing API such as automatic committing of route changes. It applies on
> top of the KVM MSI support series [1] posted recently. The complete
> stack is available at
>
>     git://git.kiszka.org/qemu-kvm.git queues/kvm-msi-irqfd
>
> If the proposes API is acceptable, I will also provide some morphing
> patches for qemu-kvm to make the merge of both trees smoother.
>
> After this series, to only reasons to still use qemu-kvm for production
> purposes will be PCI device assignment and potential dependencies on
> legacy command line switches as well as vmstate formats (when requiring
> backward migration support). However, the majority of users should be
> able to switch to upstream QEMU seamlessly and finally receive the same
> level of performance on x86.
>
>

Thanks, applied.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2012-05-20 14:20 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 ` Avi Kivity [this message]
2012-05-20 14:20   ` [Qemu-devel] [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost 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
2012-05-21 11:35         ` [Qemu-devel] " 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=4FB8FDA6.3070001@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --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.