aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts-by-pid.py
diff options
context:
space:
mode:
authorChia-I Wu <[email protected]>2019-04-29 15:08:23 -0700
committerGerd Hoffmann <[email protected]>2019-05-06 10:52:58 +0200
commitefe2bf965522bf0796d413b47a2abbf81d471d6f (patch)
tree18cbfaf4bfe4bfb5352a30bb9b47d7f598aa2d4b /tools/perf/scripts/python/syscall-counts-by-pid.py
parent1f358bc6f272b9846dda4c1a9ab05aa1afa06954 (diff)
drm/virtio: set seqno for dma-fence
This is motivated by having meaningful ftrace events, but it also fixes use cases where dma_fence_is_later is called, such as in sync_file_merge. In other drivers, fence creation and cmdbuf submission normally happen atomically, mutex_lock(); fence = dma_fence_create(..., ++timeline->seqno); submit_cmdbuf(); mutex_unlock(); and have no such issue. But in our driver, because most ioctls queue commands into ctrlq, we do not want to grab a lock. Instead, we set seqno to 0 when a fence is created, and update it when the command is finally queued and the seqno is known. Signed-off-by: Chia-I Wu <[email protected]> Reviewed-by: Emil Velikov <[email protected]> Link: http://patchwork.freedesktop.org/patch/msgid/[email protected] Signed-off-by: Gerd Hoffmann <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions