common/utrace: Add CS logging support
authorMark Collins <mark@igalia.com>
Thu, 20 Oct 2022 18:26:47 +0000 (18:26 +0000)
committerMarge Bot <emma+marge@anholt.net>
Fri, 11 Nov 2022 13:50:57 +0000 (13:50 +0000)
commitac5a55ef115525d5b8fcade9158fedccea24174a
tree66221bde4f071e88ea87f4ac70b70c6911a0c4d1
parent8370a0d6bfcaaf84fd7ddb58b51eb11bb416652f
common/utrace: Add CS logging support

Viewing CS traces retrieved from the driver is common practice to
determine driver bugs but there is no way to determine what
function a certain part of the CS was emitted by. This is crucial
information to determine what function is responsible for emitting
broken CS packets and to help with navigation of the CS trace.

Signed-off-by: Mark Collins <mark@igalia.com>
Reviewed-by: Danylo Piliaiev <dpiliaiev@igalia.com>
Reviewed-by: Yonggang Luo <luoyonggang@gmail.com>
Ack-by: Chia-I Wu <olvaffe@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/18271>
docs/u_trace.rst
src/util/perf/u_trace.c
src/util/perf/u_trace.h
src/util/perf/u_trace.py