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 dom0-strict > iommu option is also specified. > > The documentation goes on to say: > > "Rather than only mapping RAM pages for IOMMU accesses for Dom0, with this > option all pages up to 4GB, not marked as unusable in the E820 table, will > get a mapping established." > > This patch modifies the VT-d hardware domain initialization code such that > the workaround will continue to function in dom0-strict mode, by mapping > all pages not marked as unusable *unless* they are RAM pages not assigned > to dom0. > > Signed-off-by: Paul Durrant <paul.durr...@citrix.com>
Reviewed-by: Roger Pau Monné <roger....@citrix.com> Thanks, Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
