Re: [Xen-devel] [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges

2018-08-08 Thread Jan Beulich
>>> On 08.08.18 at 11:53, wrote: > I've lost a chunk here during one of the rebases, so the following > diff should be added to the patch in order to create maps if the iommu > page tables are shared: > > diff --git a/xen/drivers/passthrough/x86/iommu.c > b/xen/drivers/passthrough/x86/iommu.c >

Re: [Xen-devel] [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges

2018-08-08 Thread Roger Pau Monné
On Tue, Aug 07, 2018 at 04:02:43PM +0200, Roger Pau Monne wrote: > @@ -149,36 +204,9 @@ void __hwdom_init arch_iommu_hwdom_init(struct domain *d) > for ( i = 0; i < top; i++ ) > { > unsigned long pfn = pdx_to_pfn(i); > -bool map; > int rc; > > -/* > -

Re: [Xen-devel] [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges

2018-08-07 Thread Paul Durrant
Jackson > ; Tim (Xen.org) ; Julien Grall > ; Jan Beulich ; Roger Pau > Monne > Subject: [Xen-devel] [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu > option to map reserved memory ranges > > Several people have reported hardware issues (malfunctioning USB > controllers) d

[Xen-devel] [PATCH v3 4/4] x86/iommu: add reserved dom0-iommu option to map reserved memory ranges

2018-08-07 Thread Roger Pau Monne
Several people have reported hardware issues (malfunctioning USB controllers) due to iommu page faults on Intel hardware. Those faults are caused by missing RMRR (VTd) entries in the ACPI tables. Those can be worked around on VTd hardware by manually adding RMRR entries on the command line, this is