kernel/git/next/linux-next.git/drivers/dma-buf/reservation.c, branch master

dma-buf: rename reservation_object to dma_resv

2019-08-13T07:09:30+00:00

Be more consistent with the naming of the other DMA-buf objects. Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/323401/

dma-buf: nuke reservation_object seq number

2019-08-13T07:07:58+00:00

The only remaining use for this is to protect against setting a new exclusive fence while we grab both exclusive and shared. That can also be archived by looking if the exclusive fence has changed or not after completing the operation. v2: switch setting excl fence to rcu_assign_pointer Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322380/

dma-buf: further relax reservation_object_add_shared_fence

2019-08-10T10:49:28+00:00

Other cores don't busy wait any more and we removed the last user of checking the seqno for changes. Drop updating the number for shared fences altogether. Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322379/?series=64837&rev=1

dma-buf: add reservation_object_fences helper

2019-08-10T10:49:06+00:00

Add a new helper to get a consistent set of pointers from the reservation object. While at it group all access helpers together in the header file. v2: correctly return shared_count as well Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322378/?series=64837&rev=1

dma-buf: simplify reservation_object_get_fences_rcu a bit

2019-08-07T11:13:11+00:00

We can add the exclusive fence to the list after making sure we got a consistent state. Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322034/?series=64786&rev=1

dma-buf: fix shared fence list handling in reservation_object_copy_fences

2019-08-07T10:44:00+00:00

Add some helpers to correctly allocate/free reservation_object_lists. Otherwise we might forget to drop dma_fence references on list destruction. Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322031/?series=64786&rev=1

dma-buf: fix busy wait for new shared fences

2019-08-07T10:39:52+00:00

When reservation_object_add_shared_fence is replacing an old fence with a new one we should not drop the old one before the new one is in place. Otherwise other cores can busy wait for the new one to appear. Signed-off-by: Christian König Reviewed-by: Chris Wilson Link: https://patchwork.freedesktop.org/patch/322030/

dma-buf: Relax the write-seqlock for reallocating the shared fence list

2019-07-16T20:02:39+00:00

As the set of shared fences is not being changed during reallocation of the reservation list, we can skip updating the write_seqlock. Signed-off-by: Chris Wilson Cc: Daniel Vetter Cc: Christian König Reviewed-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20190712080314.21018-2-chris@chris-wilson.co.uk

dma-buf: Expand reservation_list to fill allocation

2019-07-15T11:08:05+00:00

Since kmalloc() will round up the allocation to the next slab size or page, it will normally return a pointer to a memory block bigger than we asked for. We can query for the actual size of the allocated block using ksize() and expand our variable size reservation_list to take advantage of that extra space. Signed-off-by: Chris Wilson Cc: Christian König Cc: Michel Dänzer Reviewed-by: Michel Dänzer Reviewed-by: Christian König Link: https://patchwork.freedesktop.org/patch/msgid/20190712080314.21018-1-chris@chris-wilson.co.uk

dma-buf: cleanup reservation_object_init/fini

2019-06-28T10:55:06+00:00

They are not used that often and certainly not in a hot path. Make them normal functions instead of an inline. Signed-off-by: Christian König Reviewed-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/314480/