drm/msm/gpu: Add trace events for tracking GPU submissions
authorJordan Crouse <jcrouse@codeaurora.org>
Fri, 2 Nov 2018 15:25:21 +0000 (09:25 -0600)
committerRob Clark <robdclark@gmail.com>
Tue, 11 Dec 2018 18:05:28 +0000 (13:05 -0500)
commit4241db42e474ffc6d432e60eb5aaea98f12fda20
treea5ea1eab4ce75536a43c10e42cc9f9b37d33acd0
parent568692102b6ad52fae27bef66793bc2e5770e429
drm/msm/gpu: Add trace events for tracking GPU submissions

Add trace events to track the progress of a GPU submission
msm_gpu_submit occurs at the beginning of the submissions,
msm_gpu_submit_flush happens when the submission is put on
the ringbuffer and msm_submit_flush_retired is sent when
the operation is retired.

To make it easier to track the operations a unique sequence
number is assigned to each submission and displayed in each
event output so a human or a script can easily associate
the events related to a specific submission.

Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Rob Clark <robdclark@gmail.com>
drivers/gpu/drm/msm/Makefile
drivers/gpu/drm/msm/adreno/a6xx_gpu.c
drivers/gpu/drm/msm/msm_gem.h
drivers/gpu/drm/msm/msm_gem_submit.c
drivers/gpu/drm/msm/msm_gpu.c
drivers/gpu/drm/msm/msm_gpu_trace.h [new file with mode: 0644]
drivers/gpu/drm/msm/msm_gpu_tracepoints.c [new file with mode: 0644]