Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

Am 03.07.2018 um 15:11 schrieb Daniel Vetter: On Tue, Jul 03, 2018 at 03:02:11PM +0200, Christian König wrote: Am 03.07.2018 um 14:52 schrieb Daniel Vetter: On Tue, Jul 03, 2018 at 01:46:44PM +0200, Christian König wrote: Am 25.06.2018 um 11:12 schrieb Daniel Vetter: On Mon, Jun 25, 2018 at 1

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

On Tue, Jul 03, 2018 at 03:02:11PM +0200, Christian König wrote: > Am 03.07.2018 um 14:52 schrieb Daniel Vetter: > > On Tue, Jul 03, 2018 at 01:46:44PM +0200, Christian König wrote: > > > Am 25.06.2018 um 11:12 schrieb Daniel Vetter: > > > > On Mon, Jun 25, 2018 at 10:22:31AM +0200, Daniel Vetter w

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

Am 03.07.2018 um 14:52 schrieb Daniel Vetter: On Tue, Jul 03, 2018 at 01:46:44PM +0200, Christian König wrote: Am 25.06.2018 um 11:12 schrieb Daniel Vetter: On Mon, Jun 25, 2018 at 10:22:31AM +0200, Daniel Vetter wrote: On Fri, Jun 22, 2018 at 04:11:01PM +0200, Christian König wrote: First st

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

On Tue, Jul 03, 2018 at 01:46:44PM +0200, Christian König wrote: > Am 25.06.2018 um 11:12 schrieb Daniel Vetter: > > On Mon, Jun 25, 2018 at 10:22:31AM +0200, Daniel Vetter wrote: > > > On Fri, Jun 22, 2018 at 04:11:01PM +0200, Christian König wrote: > > > > First step towards unpinned DMA buf oper

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

Am 25.06.2018 um 11:12 schrieb Daniel Vetter: On Mon, Jun 25, 2018 at 10:22:31AM +0200, Daniel Vetter wrote: On Fri, Jun 22, 2018 at 04:11:01PM +0200, Christian König wrote: First step towards unpinned DMA buf operation. I've checked the DRM drivers to potential locking of the reservation obje

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

On 06/22/2018 10:11 PM, Christian König wrote: First step towards unpinned DMA buf operation. I've checked the DRM drivers to potential locking of the reservation object, but essentially we need to audit all implementations of the dma_buf _ops for this to work. v2: reordered Signed-off-by: Chr

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

On Mon, Jun 25, 2018 at 10:22:31AM +0200, Daniel Vetter wrote: > On Fri, Jun 22, 2018 at 04:11:01PM +0200, Christian König wrote: > > First step towards unpinned DMA buf operation. > > > > I've checked the DRM drivers to potential locking of the reservation > > object, but essentially we need to a

Re: [PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

On Fri, Jun 22, 2018 at 04:11:01PM +0200, Christian König wrote: > First step towards unpinned DMA buf operation. > > I've checked the DRM drivers to potential locking of the reservation > object, but essentially we need to audit all implementations of the > dma_buf _ops for this to work. > > v2:

[PATCH 2/4] dma-buf: lock the reservation object during (un)map_dma_buf v2

First step towards unpinned DMA buf operation. I've checked the DRM drivers to potential locking of the reservation object, but essentially we need to audit all implementations of the dma_buf _ops for this to work. v2: reordered Signed-off-by: Christian König --- drivers/dma-buf/dma-buf.c | 9