Quoting Chris Wilson (2017-09-14 17:22:40)
> On some machines, the iommu cannot allocate a domain for the mock device
> causing the dma_map_sg() to fail, and the selftest to fail with -ENOMEM.
> For the mock selftests, we are using a fake device and do not care about
> iommu; so convince intel_iomm
Quoting Matthew Auld (2017-09-18 16:32:19)
> On 18 September 2017 at 15:22, Chris Wilson wrote:
> > Quoting Chris Wilson (2017-09-14 17:22:40)
> >> On some machines, the iommu cannot allocate a domain for the mock device
> >> causing the dma_map_sg() to fail, and the selftest to fail with -ENOMEM.
On 18 September 2017 at 15:22, Chris Wilson wrote:
> Quoting Chris Wilson (2017-09-14 17:22:40)
>> On some machines, the iommu cannot allocate a domain for the mock device
>> causing the dma_map_sg() to fail, and the selftest to fail with -ENOMEM.
>> For the mock selftests, we are using a fake dev
Quoting Chris Wilson (2017-09-14 17:22:40)
> On some machines, the iommu cannot allocate a domain for the mock device
> causing the dma_map_sg() to fail, and the selftest to fail with -ENOMEM.
> For the mock selftests, we are using a fake device and do not care about
> iommu; so convince intel_iomm
On some machines, the iommu cannot allocate a domain for the mock device
causing the dma_map_sg() to fail, and the selftest to fail with -ENOMEM.
For the mock selftests, we are using a fake device and do not care about
iommu; so convince intel_iommu to treat us as a dummy device with an
identity ma
