From: "Jan Beulich" <JBeulich@suse.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Boris Ostrovsky <boris.ostrovsky@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one
Date: Wed, 06 Feb 2013 12:52:38 +0000 [thread overview]
Message-ID: <5112602602000078000BC725@nat28.tlf.novell.com> (raw)
In-Reply-To: <364251457.20130206122422@eikelenboom.it>
>>> On 06.02.13 at 12:24, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> Hmm with the patch it does boot, but disables the I/O virtualization.
Good. While, as said before, I still don't understand why it didn't
crash earlier without that patch, I'm glad it's fixed. Will post the
patch for inclusion momentarily.
> Output of xl-dmesg attached, do you still need a xen-sums of the situation
> without the debug patch (where it does crash) ?
And you can't expect much else with broken ACPI tables:
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0xd7
(XEN) AMD-Vi: IVHD Special: 0000:00:14.0 variety 0x2 handle 0
This is a HPET entry.
(XEN) AMD-Vi: IVHD Device Entry: type 0x48 id 0 flags 0
(XEN) AMD-Vi: IVHD Special: 0000:00:00.1 variety 0x1 handle 0x7
And this is an entry for IO-APIC #2 (ID 7), whereas FADT says
(XEN) ACPI: IOAPIC (id[0x06] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 6, version 33, address 0xfec00000, GSI 0-23
(XEN) ACPI: IOAPIC (id[0x07] address[0xfec20000] gsi_base[24])
(XEN) IOAPIC[1]: apic_id 7, version 33, address 0xfec20000, GSI 24-55
so the IOMMU table is lacking an entry for the first IO-APIC, and
without that we can't set up per-device interrupt remapping (in
which case we choose to disable the IOMMU altogether, albeit it
had been questioned whether that isn't making a bad situation
worse in some cases).
If you want the IOMMU back (at the price of re-opening the
security issue described in XSA-36), you'd have to pass
"iommu=amd-iommu-perdev-intremap" to the hypervisor.
Jan
next prev parent reply other threads:[~2013-02-06 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 21:19 Xen-unstable boot panic due to changeset 26517 AMD, IOMMU: Clean up old entries in remapping tables when creating new one Sander Eikelenboom
2013-02-06 10:23 ` Jan Beulich
2013-02-06 11:24 ` Sander Eikelenboom
2013-02-06 12:52 ` Jan Beulich [this message]
2013-02-06 13:39 ` Sander Eikelenboom
2013-02-06 21:34 ` Sander Eikelenboom
2013-02-08 20:14 ` Suravee Suthikulanit
2013-02-08 20:34 ` Sander Eikelenboom
2013-02-12 8:50 ` Jan Beulich
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=5112602602000078000BC725@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@amd.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.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.