From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree
Date: Thu, 13 Aug 2009 12:00:03 +0300 [thread overview]
Message-ID: <4A83D613.5070408@redhat.com> (raw)
In-Reply-To: <4A833B9C.6000803@codemonkey.ws>
On 08/13/2009 01:01 AM, Anthony Liguori wrote:
> Christoph Hellwig wrote:
>> On Wed, Aug 12, 2009 at 01:00:59PM +0300, Avi Kivity wrote:
>>>> Looks like a irq routing issue ...
>>> What about qemu-kvm.git (and its bios)? There was a lot of irq
>>> routing work there, maybe not all of it made it into qemu.git.
>>
>> Yeah, qemu-kvm works just fine. The amount of irq routing trouble I see
>> with virtio and upstream qemu is getting really annoying :P
>
> Where were the irq routing trouble fixes in qemu-kvm? Was it fixes in
> the BIOS?
>
I think so, but not 100% sure.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-13 9:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 23:56 [Qemu-devel] virtio-blk/qdev failure in the current git tree Christoph Hellwig
2009-08-11 0:29 ` Anthony Liguori
2009-08-11 16:13 ` Christoph Hellwig
2009-08-11 16:36 ` Christoph Hellwig
2009-08-11 18:45 ` Anthony Liguori
2009-08-11 19:28 ` Gerd Hoffmann
2009-08-12 9:26 ` Gerd Hoffmann
2009-08-12 10:00 ` Avi Kivity
2009-08-12 10:19 ` Gerd Hoffmann
2009-08-12 10:40 ` Gerd Hoffmann
2009-08-12 10:51 ` Avi Kivity
2009-08-12 11:45 ` Reimar Döffinger
2009-08-12 21:50 ` Christoph Hellwig
2009-08-12 22:01 ` Anthony Liguori
2009-08-13 9:00 ` Avi Kivity [this message]
2009-08-13 12:07 ` Gerd Hoffmann
2009-08-13 12:47 ` Gerd Hoffmann
2009-08-13 13:15 ` Anthony Liguori
2009-08-13 13:38 ` Gerd Hoffmann
2009-08-12 10:08 ` Gerd Hoffmann
2009-08-12 21:54 ` Christoph Hellwig
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=4A83D613.5070408@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=hch@lst.de \
--cc=kraxel@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.