[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

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



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.