linux

iv/linux

History

Chris Wilson 0fc89b6802 dma-fence: Simply wrap dma_fence_signal_locked with dma_fence_signal

Currently dma_fence_signal() tries to avoid the spinlock and only takes
it if absolutely required to walk the callback list. However, to allow
for some users to surreptitiously insert lazy signal callbacks that
do not depend on enabling the signaling mechanism around every fence,
we always need to notify the callbacks on signaling. As such, we will
always need to take the spinlock and dma_fence_signal() effectively
becomes a clone of dma_fence_signal_locked().

v2: Update the test_and_set_bit() before entering the spinlock.
v3: Drop the test_[and_set]_bit() before the spinlock, it's a caller
error so expected to be very unlikely.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Christian König <christian.koenig@amd.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Christian König <christian.koenig@amd.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190817152300.5370-1-chris@chris-wilson.co.uk

2019-08-17 18:03:12 +01:00

dma-buf.c

dma-buf: Restore seqlock around dma_resv updates

2019-08-16 12:40:58 +01:00

dma-fence-array.c

dma-fence: Propagate errors to dma-fence-array container

2019-08-12 08:25:52 +01:00

dma-fence-chain.c

dma-buf: fix stack corruption in dma_fence_chain_release

2019-08-05 17:32:33 +02:00

dma-fence.c

dma-fence: Simply wrap dma_fence_signal_locked with dma_fence_signal