qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree
Date: Wed, 12 Aug 2009 13:45:03 +0200	[thread overview]
Message-ID: <20090812114503.GA11394@1und1.de> (raw)
In-Reply-To: <4A829EAB.8070706@redhat.com>

On Wed, Aug 12, 2009 at 01:51:23PM +0300, Avi Kivity wrote:
> On 08/12/2009 01:40 PM, Gerd Hoffmann wrote:
> >  ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> > +ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
> > +ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
> > +ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
> > +ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
> >  ACPI: IRQ0 used by override.
> >  ACPI: IRQ2 used by override.
> > +ACPI: IRQ5 used by override.
> >  ACPI: IRQ9 used by override.
> > +ACPI: IRQ10 used by override.
> > +ACPI: IRQ11 used by override.
> >
> > !!!
> 
> The qemu ioapic doesn't implement polarity, so it happily boots with the 
> lines inverted.
> 
> >  ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> > -ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
> > -ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12)
> > -ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11 12)
> > -ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12)
> > +ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
> > +ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
> > +ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
> > +ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
> >
> > !!!
> >
> > That indeed looks like a bunch of changes and/or fixes did not find 
> > the way to upstream qemu ...
> 
> Yeah.

I don't have much of a clue, but I in case it matters can say that with
qemu-kvm latest git I had quite a few issues with the eepro100 interrupts
never being processed (that was Mac OS X though), probably getting lost somewhere.
So I'd be very careful about some of those changes (I was too lazy to
investigate, since qemu --enable-kvm just worked ;-) )...

  reply	other threads:[~2009-08-12 11:51 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 [this message]
2009-08-12 21:50             ` Christoph Hellwig
2009-08-12 22:01               ` Anthony Liguori
2009-08-13  9:00                 ` Avi Kivity
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=20090812114503.GA11394@1und1.de \
    --to=reimar.doeffinger@gmx.de \
    --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;
as well as URLs for NNTP newsgroup(s).