> > From: Robin Murphy <robin.murphy@xxxxxxx> > > > > drm_gem_cma_mmap() cannot assume every implementation of dma_mmap_wc() > > will end up calling remap_pfn_range() (which happens to set the relevant > > vma flag, among others), so in order to make sure expectations around > > VM_DONTEXPAND are met, let it explicitly set the flag like most other > > GEM mmap implementations do. > > > > This avoids repeated warnings on a small minority of systems where the > > display is behind an IOMMU, and has a simple driver which does not > > override drm_gem_cma_default_funcs. Arm hdlcd is an in-tree affected > > driver. Out-of-tree, the Apple DCP driver is affected; this fix is > > required for DCP to be mainlined. > > How/where does this warn? Also there should be a lot more drivers than > just these two which have an iommu for the display block, so this not > working is definitely a more wide-spread issue. To summarize our discussion on IRC: This fails `WARN_ON(!(vma->vm_flags & VM_DONTEXPAND))` in drm_gem_mmap_obj. This warning was introduced in Oct 2019. For a driver to hit this code path, it must use the CMA helpers without overriding dem_gem_cma_default_funcs, but use CMA backed by a hardware IOMMU instead of a physical carveout. This means popular drivers don't hit this warning: normal drivers that use CMA do so with a carveout instead of an IOMMU, and normal drivers with an IOMMU do not use the default CMA helpers. hdlcd is one of the few drivers hitting this, but hdlcd gets very little testing. Seeing as the last significant change to hdlcd was in May 2019, it's believable that nobody noticed until Robin hit this WARN and typed out this patch, especially as the driver still works despite the WARN.
