All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bret Ketchum <Bret_Ketchum@dell.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	"Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Q35 FreeBSD install status
Date: Tue, 17 Sep 2013 19:44:01 +0300	[thread overview]
Message-ID: <20130917164401.GC20672@redhat.com> (raw)
In-Reply-To: <827924efb2d643a88405433b94e9c3f6@mspexmb1.Beer.Town>


Could be MPT is not parsed correctly?
I see that we put 0 in the ID in bios code.
Could you dump the MPT and send it on list?

On Tue, Sep 17, 2013 at 03:25:38PM +0000, Bret Ketchum wrote:
> 
>     The emulated e1000 uses legacy interrupts. I'm wondering if someone can help me understand the mptable (used by FreeBSD to route interrupts and defined in Intel's MP spec):
> 
> Bus:            Bus ID  Type
>                  0       PCI
>                  1       ISA
> 
> I/O APICs:      APIC ID Version State           Address
>                  0       0x11    usable          0xfec00000
> 
> I/O Ints:       Type    Polarity    Trigger     Bus ID   IRQ    APIC ID    PIN#
>                 INT     active-hi    conforms        0    31:A        2    10
>                 INT     active-hi    conforms        0     3:A        2    11
> 
> 
>      The interrupts associated with the PCI bus where e1000 hangs suggest there is an APIC with an ID of  2 but there is only one APIC (with an ID of 0). 
> 
> -----Original Message-----
> From: Gerd Hoffmann [mailto:kraxel@redhat.com] 
> Sent: Monday, September 16, 2013 10:15 AM
> To: Bret Ketchum
> Cc: Qemu-devel@nongnu.org; mst@redhat.com
> Subject: Re: [Qemu-devel] Q35 FreeBSD install status
> 
> On Mo, 2013-09-16 at 12:57 +0000, Bret Ketchum wrote:
> >     Tried that - looks like FreeBSD expects to use MSI for AHCI devices which does not appear to be supported in q35.
> 
> It is supported and linux has no problems using ahci with msi.
> 
> Given that e1000 seems to have interrupt problems too I wouldn't be surprised if both issues have the same root cause.  Might be something in the seabios acpi tables.  Or a bug in FreeBSD.
> 
> cheers,
>   Gerd
> 
> 
> 

  reply	other threads:[~2013-09-17 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 16:16 [Qemu-devel] Q35 FreeBSD install status Bret Ketchum
2013-09-10 17:29 ` Michael S. Tsirkin
2013-09-10 17:29   ` Bret Ketchum
2013-09-10 17:49     ` Michael S. Tsirkin
2013-09-16 12:28       ` Bret Ketchum
2013-09-16 12:36         ` Michael S. Tsirkin
2013-09-16 13:03           ` Bret Ketchum
2013-09-16 13:07           ` Bret Ketchum
2013-09-16 12:55         ` Gerd Hoffmann
2013-09-16 12:57           ` Bret Ketchum
2013-09-16 15:15             ` Gerd Hoffmann
2013-09-17 15:25               ` Bret Ketchum
2013-09-17 16:44                 ` Michael S. Tsirkin [this message]
2013-09-18 12:35                   ` Bret Ketchum

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=20130917164401.GC20672@redhat.com \
    --to=mst@redhat.com \
    --cc=Bret_Ketchum@dell.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=kraxel@redhat.com \
    /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.