From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: Xen 4.2.1 boot failure with IOMMU enabled Date: Fri, 15 Feb 2013 10:21:34 -0500 Message-ID: <511E527E.6090605@oracle.com> References: <7d6022b9-fff5-4cca-b091-347d3e869909@default> <511A2FA402000078000BDAF7@nat28.tlf.novell.com> <511A33F302000078000BDB2B@nat28.tlf.novell.com> <511A35C402000078000BDB47@nat28.tlf.novell.com> <511A5DC3.4010106@oracle.com> <511A763302000078000BDC82@nat28.tlf.novell.com> <511B574902000078000BDE41@nat28.tlf.novell.com> <511B5EE102000078000BDE8A@nat28.tlf.novell.com> <511CD8C202000078000BE280@nat28.tlf.novell.com> <511CFAD4.9040905@oracle.com> <511DFE0802000078000BE95D@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <511DFE0802000078000BE95D@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: povder , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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