>>> On 17.08.18 at 13:17, wrote:
> On Fri, Aug 17, 2018 at 05:08:08AM -0600, Jan Beulich wrote:
>> >>> On 14.08.18 at 15:43, wrote:
>> > @@ -185,7 +219,13 @@ void __hwdom_init arch_iommu_hwdom_init(struct domain
>> > *d)
>> > if ( !hwdom_iommu_map(d, pfn, max_pfn) )
>> >
On Fri, Aug 17, 2018 at 05:08:08AM -0600, Jan Beulich wrote:
> >>> On 14.08.18 at 15:43, wrote:
> > @@ -185,7 +219,13 @@ void __hwdom_init arch_iommu_hwdom_init(struct domain
> > *d)
> > if ( !hwdom_iommu_map(d, pfn, max_pfn) )
> > continue;
> >
> > -rc =
>>> On 14.08.18 at 15:43, wrote:
> @@ -138,13 +139,20 @@ static bool __hwdom_init hwdom_iommu_map(const struct
> domain *d,
> unsigned long pfn,
> unsigned long max_pfn)
> {
> +unsigned int i;
> +
> /*
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
