Re: [Xen-devel] [PATCH v2 2/2] VT-d: reconcile iommu_inclusive_mapping and iommu=dom0-strict

2018-06-14 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 14 June 2018 16:59 > To: Paul Durrant > Cc: Julien Grall ; Andrew Cooper > ; Wei Liu ; George > Dunlap ; Ian Jackson ; > Kevin Tian ; Stefano Stabellini > ; xen-devel ; > Konrad Rzeszutek Wilk ; Tim (Xen.org) > >

Re: [Xen-devel] [PATCH v2 2/2] VT-d: reconcile iommu_inclusive_mapping and iommu=dom0-strict

2018-06-14 Thread Jan Beulich
>>> On 12.06.18 at 15:47, wrote: > The documentation for the iommu_inclusive_mapping Xen command line option > states: > > "Use this to work around firmware issues providing incorrect RMRR entries" > > Unfortunately this workaround does not function correctly if the dom0-strict > iommu option

Re: [Xen-devel] [PATCH v2 2/2] VT-d: reconcile iommu_inclusive_mapping and iommu=dom0-strict

2018-06-13 Thread Roger Pau Monné
On Tue, Jun 12, 2018 at 02:47:34PM +0100, Paul Durrant wrote: > The documentation for the iommu_inclusive_mapping Xen command line option > states: > > "Use this to work around firmware issues providing incorrect RMRR entries" > > Unfortunately this workaround does not function correctly if the

[Xen-devel] [PATCH v2 2/2] VT-d: reconcile iommu_inclusive_mapping and iommu=dom0-strict

2018-06-12 Thread Paul Durrant
The documentation for the iommu_inclusive_mapping Xen command line option states: "Use this to work around firmware issues providing incorrect RMRR entries" Unfortunately this workaround does not function correctly if the dom0-strict iommu option is also specified. The documentation goes on to