From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI
Date: Sun, 09 Aug 2009 20:49:23 +0300 [thread overview]
Message-ID: <4A7F0C23.8070807@redhat.com> (raw)
In-Reply-To: <20090809174100.GA17096@lst.de>
On 08/09/2009 08:41 PM, Christoph Hellwig wrote:
> On Sun, Aug 09, 2009 at 01:01:35PM +0300, Avi Kivity wrote:
>
>> Looks good. Anthony, I think this applies upstream?
>>
>
> This applies upstream, but as mentioned we can't just use it as-is.
> We'll very recent kvm kernel support for multiple MSI vectors, and
> when the host doesn't have it even 2.6.30 crashes badly in the guest.
>
Sorry, confused. Upstream doesn't use kvm for msi (everything's done in
userspace). What exactly blocks us here?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: virtio-blk performance and MSI
Date: Sun, 09 Aug 2009 20:49:23 +0300 [thread overview]
Message-ID: <4A7F0C23.8070807@redhat.com> (raw)
In-Reply-To: <20090809174100.GA17096@lst.de>
On 08/09/2009 08:41 PM, Christoph Hellwig wrote:
> On Sun, Aug 09, 2009 at 01:01:35PM +0300, Avi Kivity wrote:
>
>> Looks good. Anthony, I think this applies upstream?
>>
>
> This applies upstream, but as mentioned we can't just use it as-is.
> We'll very recent kvm kernel support for multiple MSI vectors, and
> when the host doesn't have it even 2.6.30 crashes badly in the guest.
>
Sorry, confused. Upstream doesn't use kvm for msi (everything's done in
userspace). What exactly blocks us here?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-08-09 17:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 16:35 virtio-blk performance and MSI Christoph Hellwig
2009-08-06 16:35 ` [Qemu-devel] " Christoph Hellwig
2009-08-09 10:01 ` Avi Kivity
2009-08-09 10:01 ` [Qemu-devel] " Avi Kivity
2009-08-09 17:41 ` Christoph Hellwig
2009-08-09 17:41 ` Christoph Hellwig
2009-08-09 17:49 ` Avi Kivity [this message]
2009-08-09 17:49 ` Avi Kivity
2009-08-09 19:13 ` Christoph Hellwig
2009-08-09 19:13 ` Christoph Hellwig
2009-08-09 19:53 ` Michael S. Tsirkin
2009-08-09 19:53 ` Michael S. Tsirkin
2009-08-09 19:49 ` Michael S. Tsirkin
2009-08-09 19:49 ` Michael S. Tsirkin
2009-08-09 19:56 ` Michael S. Tsirkin
2009-08-09 19:56 ` [Qemu-devel] " Michael S. Tsirkin
2009-08-11 6:05 ` Eran Rom
2009-08-11 10:30 ` Eran Rom
2009-08-11 12:14 ` Eran Rom
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=4A7F0C23.8070807@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--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.