From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Hans Mueller <mcbeagle@gmx.de>
Cc: "Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: XSA-36 / howto fix broken IVRS ACPI table
Date: Tue, 12 Mar 2013 15:41:23 -0400 [thread overview]
Message-ID: <513F84E3.9000701@oracle.com> (raw)
In-Reply-To: <123945469.jCKz4Rdygs@sheik-lin>
[-- Attachment #1.1: Type: text/plain, Size: 4379 bytes --]
On 03/12/2013 03:04 PM, Hans Mueller wrote:
> Hello,
>
> since applying the patches related to XSA-36 Xen recognizes a broken IVRS ACPI
> table and disables I/O virtualisation.
>
> I contacted the manufacturer of the mainboard/BIOS and they want to help me by
> providing a patched BIOS - so far so good.
>
> However, they need details about what to fix, which I don't know either.
>
> Could you pls. give me some hints which I can forward to the manufacturer
> support?
They should look at AMD IOMMU spec. For example,
support.amd.com/us/Processor_TechDocs/48882.pdf. Tables 77 and 79.
More specifically, the problem is these two entries:
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0x0 flags 0xd7
(XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x1 handle 0x8
..
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0x0 flags 0x0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x8
which tell IOMMU driver that there are two IOAPICs, both with APICID 8.
I believe the second one is wrong.
-boris
>
> Thanks a lot & best regards
> Hans
>
>
>
> PS: Hardware is a Gigabyte GA-970A-UD3(rev. 1.0), BIOS F7 (tested F8a, too).
>
> PPS: I know about 'no-amd-iommu-perdev-intremap' - this does not really help
> as e.g. heavy i/o on a usb device in one domain causes other domains to
> disable the related irq etc. ...
>
>
>
> From the support mail:
> "Our hardware team replied:
>
> Please inform us what settings or specific detail he needs to modify on IVRS
> ACPI Table.
> They will try to patch it in a special BIOS and ask customer to check.
> Or maybe you can ask Xen for a proper IVRS ACPI Table form/example and send to
> us.
> We can study on this and provide a special BIOS."
>
>
>
> From 'xl dmesg':
> (XEN) AMD-Vi: Found MSI capability block at 0x54
> (XEN) AMD-Vi: ACPI Table:
> (XEN) AMD-Vi: Signature IVRS
> (XEN) AMD-Vi: Length 0xd0
> (XEN) AMD-Vi: Revision 0x1
> (XEN) AMD-Vi: CheckSum 0x9b
> (XEN) AMD-Vi: OEM_Id AMD
> (XEN) AMD-Vi: OEM_Table_Id RD890S
> (XEN) AMD-Vi: OEM_Revision 0x202031
> (XEN) AMD-Vi: Creator_Id AMD
> (XEN) AMD-Vi: Creator_Revision 0x0
> (XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xa0 id 0x2
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x0 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x0 -> 0x2
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x10 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x100 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x100 -> 0x101
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x38 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x200 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x48 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x300 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0x88 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x90 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x90 -> 0x92
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x98 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x98 -> 0x9a
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa0 flags 0xd7
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa3 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa4 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x0 id 0x0 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x43 id 0x400 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x400 -> 0x4ff alias 0xa4
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa5 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x2 id 0xa8 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x500 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0x500 -> 0x5ff
> (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0xb0 flags 0x0
> (XEN) AMD-Vi: Dev_Id Range: 0xb0 -> 0xb2
> (XEN) AMD-Vi: IVHD Device Entry: type 0x0 id 0x0 flags 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0x0 flags 0xd7
> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x1 handle 0x8
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0x0 flags 0xd7
> (XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0x0
> (XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0x0 flags 0x0
> (XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x8
> (XEN) IVHD Error: Conflicting IO-APIC 0x8 entries
> (XEN) AMD-Vi: Error initialization
> (XEN) I/O virtualisation disabled
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 5119 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-03-12 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 19:04 XSA-36 / howto fix broken IVRS ACPI table Hans Mueller
2013-03-12 19:41 ` Boris Ostrovsky [this message]
2013-04-23 17:11 ` Hans Mueller
2013-04-24 6:47 ` Jan Beulich
2013-04-24 20:03 ` Hans Mueller
2013-04-25 9:36 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2013-04-16 7:20 Eric Shelton
2013-04-23 23:39 Eric Shelton
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=513F84E3.9000701@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=mcbeagle@gmx.de \
--cc=xen-devel@lists.xen.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.