From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: povder <povder@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.2.1 boot failure with IOMMU enabled
Date: Fri, 15 Feb 2013 10:21:34 -0500 [thread overview]
Message-ID: <511E527E.6090605@oracle.com> (raw)
In-Reply-To: <511DFE0802000078000BE95D@nat28.tlf.novell.com>
On 02/15/2013 03:21 AM, Jan Beulich wrote:
>
> But I don't think we can easily deal with the single IOMMU
> case, making that IOMMU cover all devices, as we would
> still need to figure out the requestor ID for each device. That
> requires looking at the PCI bus topology iiuc, and while we
> have the necessary logic for VT-d, it seems not really strait
> forward (mainly because risky) to make use of this in the AMD Vi
> code too.
Scanning PCI for devices would effectively mean that we are ignoring
IVHD (device portion of IVRS). That would be somewhat unfortunate (but
maybe unavoidable, given the state of BIOSes).
-boris
next prev parent reply other threads:[~2013-02-15 15:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 3:20 Xen 4.2.1 boot failure with IOMMU enabled Boris Ostrovsky
2013-02-12 6:26 ` povder
2013-02-12 10:06 ` Jan Beulich
2013-02-12 10:55 ` povder
2013-02-12 11:03 ` Jan Beulich
2013-02-12 11:15 ` povder
2013-02-12 11:22 ` Jan Beulich
2013-02-12 11:29 ` Jan Beulich
2013-02-12 15:20 ` Boris Ostrovsky
2013-02-12 15:50 ` povder
2013-02-12 16:04 ` Jan Beulich
2013-02-12 17:44 ` povder
2013-02-12 18:23 ` povder
2013-02-12 18:40 ` povder
2013-02-13 8:05 ` Jan Beulich
2013-02-13 8:28 ` povder
2013-02-13 8:37 ` Jan Beulich
2013-02-13 18:21 ` povder
2013-02-14 11:03 ` Jan Beulich
2013-02-14 11:29 ` Jan Beulich
2013-02-14 14:55 ` Boris Ostrovsky
2013-02-15 8:21 ` Jan Beulich
2013-02-15 15:21 ` Boris Ostrovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-13 1:33 Boris Ostrovsky
2013-02-13 8:24 ` Jan Beulich
2013-02-11 17:31 povder
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=511E527E.6090605@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=povder@gmail.com \
--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.