WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue

Subject: Re: [Xen-devel] iommu: mapping reserved region failed - Q35 -VT-DIssue
From: Stefan Bauer <stefan.bauer@xxxxxxxxxxx>
Date: Fri, 31 Oct 2008 14:31:06 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 31 Oct 2008 06:31:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <409D32C55C48D34DB5E31C8AB29EB15B071C760D@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <49089D18.4030405@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C6E25@xxxxxxxxxxxxxxxxxxxxxx><4908B669.7080108@xxxxxxxxxxx><409D32C55C48D34DB5E31C8AB29EB15B071C6E74@xxxxxxxxxxxxxxxxxxxxxx> <4908BC3C.3070307@xxxxxxxxxxx> <409D32C55C48D34DB5E31C8AB29EB15B071C6EA7@xxxxxxxxxxxxxxxxxxxxxx> <4908C6FC.9030307@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686CF47@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49096151.8090500@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686D126@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49098860.9050309@xxxxxxxxxxx> <715D42877B251141A38726ABF5CABF2C018686D17B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><4909C811.9070105@xxxxxxxxxxx><715D42877B251141A38726ABF5CABF2C018686D23C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <490AB8FC.1020807@xxxxxxxxxxx> <409D32C55C48D34DB5E31C8AB29EB15B071C760D@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla - wenns mal wieder laenger dauert
Ross Philipson schrieb:
> Stefan,
> 
> Most of the paths through the function domain_context_mapping() (in
> xen/drivers/passthrough/vtd/iommu.c) also trace extra information but I
> don't see those traces so it is reasonable to assume that the function
> is returning an error when the call to acpi_find_matched_drhd_unit()
> fails to find a DRHD for the particular device. I would start by putting
> a trace there in the failure case and trace out the bus/dev info
> (presumably it is device 00:03.2). If this is the case then we can look
> at your DMAR ACPI table - maybe this is a faulty BIOS issue (e.g. there
> is no DRHD reporting INCLUDE_ALL devices).

Sorry but thats a way to technically for me. I'm not familiar with C
nor any other higher programming language. I will provide informations
and do testing.

> Or I may be wrong and the logging level is just not set for those
> gdprintk() calls in trace in the switch statement (though I don't think
> this is the case). If it is the case put code after the various calls in
> the switch statement to test the "ret" value and trace an error if it

Regards

-- 
Stefan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>