diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2019-10-04 11:11:40 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2019-10-04 11:43:45 +0100 |
commit | 9c98f021e4e717ffd9948fa65340ea3ef12b7935 (patch) | |
tree | 4458262a321fc98ac62db85d30b57dae0648b9e1 /mm | |
parent | bebf00512cc2c2a942a6dc47674bf44b7a3cb681 (diff) | |
download | linux-9c98f021e4e717ffd9948fa65340ea3ef12b7935.tar.gz linux-9c98f021e4e717ffd9948fa65340ea3ef12b7935.tar.bz2 linux-9c98f021e4e717ffd9948fa65340ea3ef12b7935.zip |
dma-fence: Serialise signal enabling (dma_fence_enable_sw_signaling)
Make dma_fence_enable_sw_signaling() behave like its
dma_fence_add_callback() and dma_fence_default_wait() counterparts and
perform the test to enable signaling under the fence->lock, along with
the action to do so. This ensure that should an implementation be trying
to flush the cb_list (by signaling) on retirement before freeing the
fence, it can do so in a race-free manner.
See also 0fc89b6802ba ("dma-fence: Simply wrap dma_fence_signal_locked
with dma_fence_signal").
v2: Refactor all 3 enable_signaling paths to use a common function.
v3: Don't argue, just keep the tracepoint in the existing spot.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191004101140.32713-1-chris@chris-wilson.co.uk
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions