All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree
Date: Wed, 12 Aug 2009 12:40:11 +0200	[thread overview]
Message-ID: <4A829C0B.3070705@redhat.com> (raw)
In-Reply-To: <4A82973A.5070005@redhat.com>

On 08/12/09 12:19, Gerd Hoffmann wrote:
> On 08/12/09 12:00, Avi Kivity wrote:
>> What about qemu-kvm.git (and its bios)?
>
> Works:
>
> ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKB] -> GSI 10 (level,
> high) -> IRQ 10

 From boot log diff:

--- qemu.log    2009-08-12 12:26:30.000000000 +0200
+++ kvm.log     2009-08-12 12:20:22.000000000 +0200
@@ -26,21 +26,43 @@
  ACPI: PM-Timer IO Port: 0xb008
  ACPI: Local APIC address 0xfee00000
  ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
-Processor #0 6:2 APIC version 17
+Processor #0 6:2 APIC version 20

Where does this come from?  kernel vs. userspace apic?

+ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
+ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
[ more of these ]

For hotplug cpus I guess?

  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.

!!!

  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 ...

cheers,
   Gerd

  reply	other threads:[~2009-08-12 10:40 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 [this message]
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
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=4A829C0B.3070705@redhat.com \
    --to=kraxel@redhat.com \
    --cc=avi@redhat.com \
    --cc=hch@lst.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 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.