On Mon, Nov 18, 2019 at 11:35:22AM +0100, Daniel Vetter wrote:
> A few reasons to drop kmap:
>
> - For native objects all we do is look at obj->vaddr anyway, so might
> as well not call functions for every page.
>
> - Reloc-processing on dma-buf is ... questionable.
>
> - Plus most dma-buf tha
On Mon, Nov 25, 2019 at 10:58:56AM +0100, Daniel Vetter wrote:
> On Mon, Nov 18, 2019 at 11:35:22AM +0100, Daniel Vetter wrote:
> > A few reasons to drop kmap:
> >
> > - For native objects all we do is look at obj->vaddr anyway, so might
> > as well not call functions for every page.
> >
> > -
On Mon, Nov 18, 2019 at 11:35:22AM +0100, Daniel Vetter wrote:
> A few reasons to drop kmap:
>
> - For native objects all we do is look at obj->vaddr anyway, so might
> as well not call functions for every page.
>
> - Reloc-processing on dma-buf is ... questionable.
>
> - Plus most dma-buf tha
A few reasons to drop kmap:
- For native objects all we do is look at obj->vaddr anyway, so might
as well not call functions for every page.
- Reloc-processing on dma-buf is ... questionable.
- Plus most dma-buf that bother kernel cpu mmaps give you at least
vmap, much less kmaps. And all th
