aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/msm/msm_gpu_trace.h
AgeCommit message (Collapse)AuthorFilesLines
2020-09-12drm/msm/gpu: Add suspend/resume tracepointsRob Clark1-0/+26
Signed-off-by: Rob Clark <[email protected]>
2020-09-09drm/msm: Convert shrinker msgs to tracepointsRob Clark1-0/+26
This reduces the spam in dmesg when we start hitting the shrinker, and replaces it with something we can put on a timeline while profiling or debugging system issues. Signed-off-by: Rob Clark <[email protected]> Reviewed-by: Jordan Crouse <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]>
2020-09-09drm/msm/gpu: Add GPU freq_change tracesRob Clark1-0/+31
Technically the GMU specific one is a bit redundant, but it was useful to track down a bug. Signed-off-by: Rob Clark <[email protected]> Reviewed-by: Jordan Crouse <[email protected]>
2019-09-03drm/msm: add atomic tracesRob Clark1-1/+1
This was useful for debugging fps drops. I suspect it will be useful again. Signed-off-by: Rob Clark <[email protected]> Reviewed-by: Sean Paul <[email protected]>
2018-12-11drm/msm/gpu: Add trace events for tracking GPU submissionsJordan Crouse1-0/+90
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 <[email protected]> Signed-off-by: Rob Clark <[email protected]>