Messages in this thread |  | | Date | Wed, 30 Sep 2020 11:02:52 +0200 | From | Christoph Hellwig <> | Subject | Re: linux-next: build failure after merge of the drm tree |
| |
On Mon, Sep 28, 2020 at 03:31:28PM +0200, Paul Cercueil wrote: > It's allocated with dma_alloc_wc, but then it's only accessed as > non-coherent. > > Anyway, for the time being I guess you could revert 37054fc81443. But I > have patches on top of it in drm-misc-next so it's going to be a mess. > > If we have time I can come up with a custom dumb_create() fonction, to make > sure that the GEM buffers are allocated with dma_alloc_noncoherent(). Is > there a dma_mmap_noncoherent() too?
Please use the lower-level dma_alloc_pages and then just insert the pages directly using remap_pfn_range. Although it might make sense to eventually create a wrapper around remap_pfn_range for all the vma sizing sanity checks.
> > -Paul > ---end quoted text---
|  |