qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bret Ketchum <Bret_Ketchum@DELL.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	"Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Q35 FreeBSD install status
Date: Wed, 18 Sep 2013 12:35:27 +0000	[thread overview]
Message-ID: <e82d38b1a29649ee832002ac6033dd25@mspexmb2.Beer.Town> (raw)
In-Reply-To: <20130917164401.GC20672@redhat.com>


    For those following along. The mptable I presented was an old table, updating to SeaBIOS 1.7.3 fixed that but still no interrupts. However, it appears FreeBSD has trouble parsing the ACPI tables presented via q35-acpi-dsdt.aml as it does not create the sysresource devices associated with ACPI. A work around until I uncover the parsing issue it to revert to using the mptable to wire PCI interrupts via 'debug.acpi.disabled=pci_link'. FreeBSD will whine about failing to force attach of GSIs but thus far all seems to be well with the world. I've yet to check but I suspect the parsing issue is also root cause of uhci/ehci missing interrupts.

-----Original Message-----
From: Michael S. Tsirkin [mailto:mst@redhat.com] 
Sent: Tuesday, September 17, 2013 11:44 AM
To: Bret Ketchum
Cc: Gerd Hoffmann; Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Q35 FreeBSD install status


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-18 12:35 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
2013-09-18 12:35                   ` Bret Ketchum [this message]

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=e82d38b1a29649ee832002ac6033dd25@mspexmb2.Beer.Town \
    --to=bret_ketchum@dell.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=kraxel@redhat.com \
    --cc=mst@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 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).