Re: RFC: unpinned DMA-buf exporting v2

2018-03-19 Thread Daniel Vetter
On Fri, Mar 16, 2018 at 02:20:44PM +0100, Christian König wrote: > Hi everybody, > > since I've got positive feedback from Daniel I continued working on this > approach. > > A few issues are still open: > 1. Daniel suggested that I make the invalidate_mappings callback a parameter > of dma_buf_

Re: RFC: unpinned DMA-buf exporting

2018-03-12 Thread Daniel Vetter
On Mon, Mar 12, 2018 at 8:15 PM, Christian König wrote: > Am 12.03.2018 um 18:24 schrieb Daniel Vetter: >> >> On Fri, Mar 09, 2018 at 08:11:40PM +0100, Christian K??nig wrote: >>> >>> This set of patches adds an option invalidate_mappings callback to each >>> DMA-buf attachment which can be filled

Re: RFC: unpinned DMA-buf exporting

2018-03-12 Thread Christian König
Am 12.03.2018 um 18:24 schrieb Daniel Vetter: On Fri, Mar 09, 2018 at 08:11:40PM +0100, Christian K??nig wrote: This set of patches adds an option invalidate_mappings callback to each DMA-buf attachment which can be filled in by the importer. This callback allows the exporter to provided the DM

Re: RFC: unpinned DMA-buf exporting

2018-03-12 Thread Daniel Vetter
On Fri, Mar 09, 2018 at 08:11:40PM +0100, Christian K??nig wrote: > This set of patches adds an option invalidate_mappings callback to each > DMA-buf attachment which can be filled in by the importer. > > This callback allows the exporter to provided the DMA-buf content > without pinning it. The r