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>
Showing
- drivers/gpu/drm/msm/Makefile 2 additions, 1 deletiondrivers/gpu/drm/msm/Makefile
- drivers/gpu/drm/msm/adreno/a6xx_gpu.c 7 additions, 0 deletionsdrivers/gpu/drm/msm/adreno/a6xx_gpu.c
- drivers/gpu/drm/msm/msm_gem.h 1 addition, 0 deletionsdrivers/gpu/drm/msm/msm_gem.h
- drivers/gpu/drm/msm/msm_gem_submit.c 12 additions, 3 deletionsdrivers/gpu/drm/msm/msm_gem_submit.c
- drivers/gpu/drm/msm/msm_gpu.c 21 additions, 2 deletionsdrivers/gpu/drm/msm/msm_gpu.c
- drivers/gpu/drm/msm/msm_gpu_trace.h 90 additions, 0 deletionsdrivers/gpu/drm/msm/msm_gpu_trace.h
- drivers/gpu/drm/msm/msm_gpu_tracepoints.c 6 additions, 0 deletionsdrivers/gpu/drm/msm/msm_gpu_tracepoints.c
Loading
Please register or sign in to comment