From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [RFC][PATCH 0/2] uq/master: Basic MSI support for in-kernel irqchip mode
Date: Wed, 28 Mar 2012 09:13:22 +0200 [thread overview]
Message-ID: <4F72BA12.2080309@web.de> (raw)
In-Reply-To: <cover.1332371825.git.jan.kiszka@web.de>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
On 2012-03-22 00:17, Jan Kiszka wrote:
> Some half a year ago when I posted my first attempt to refactor MSI
> for KVM support, we came to the conclusion that it might suffice to do
> transparent dynamic routing for user-space injected MSI messages. These
> two patches now implement such an approach for upstream.
>
> As QEMU does not yet include irqfd support (for vhost) or pci device
> assignment, this is already enough to enable MSI over the in-kernel
> irqchip. Still, this is only RFC as it is just lightly tested and should
> primarily collect feedback regarding the direction. If it's fine, I'd
> like to base further qemu-kvm refactorings and upstream preparations on
> top of such a series.
>
> Also, I'd like to reanimate my KVM patch to provide direct MSI injection
> in future kernels so that we do not need to take this long path here
> forever.
>
> Jan Kiszka (2):
> kvm: Introduce basic MSI support in-kernel irqchips
> KVM: x86: Wire up MSI support for in-kernel irqchip
>
> hw/apic.c | 3 +
> hw/kvm/apic.c | 33 ++++++++++-
> hw/pc.c | 5 --
> kvm-all.c | 171 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> kvm.h | 1 +
> 5 files changed, 205 insertions(+), 8 deletions(-)
>
Anyone any comments? I think this series could open the door for
kernel_irqchip=on as default in QEMU 1.1.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-03-28 7:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 23:17 [RFC][PATCH 0/2] uq/master: Basic MSI support for in-kernel irqchip mode Jan Kiszka
2012-03-21 23:17 ` [RFC][PATCH 1/2] kvm: Introduce basic MSI support in-kernel irqchips Jan Kiszka
2012-03-28 11:09 ` Avi Kivity
2012-03-28 11:26 ` Michael S. Tsirkin
2012-03-28 11:33 ` Jan Kiszka
2012-03-28 11:44 ` Avi Kivity
2012-03-28 11:54 ` Jan Kiszka
2012-03-28 12:32 ` Avi Kivity
2012-03-28 12:49 ` Jan Kiszka
2012-03-28 15:44 ` Michael S. Tsirkin
2012-03-21 23:17 ` [RFC][PATCH 2/2] KVM: x86: Wire up MSI support for in-kernel irqchip Jan Kiszka
2012-03-28 7:13 ` Jan Kiszka [this message]
2012-03-28 9:45 ` [RFC][PATCH 0/2] uq/master: Basic MSI support for in-kernel irqchip mode Michael S. Tsirkin
2012-03-28 9:50 ` Jan Kiszka
2012-03-28 10:47 ` Michael S. Tsirkin
2012-03-28 11:07 ` Jan Kiszka
2012-03-28 11:31 ` Michael S. Tsirkin
2012-03-28 11:36 ` Jan Kiszka
2012-03-28 15:43 ` Michael S. Tsirkin
2012-03-28 16:00 ` Jan Kiszka
2012-03-28 16:30 ` Michael S. Tsirkin
2012-03-28 16:53 ` Jan Kiszka
2012-03-28 17:06 ` Michael S. Tsirkin
2012-03-28 17:18 ` Jan Kiszka
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=4F72BA12.2080309@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox