aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorRodrigo Vivi <[email protected]>2023-11-22 14:38:29 +0000
committerRodrigo Vivi <[email protected]>2023-12-21 11:45:19 -0500
commit4016d6bf368c4894c834e0652aecd93f7d2a2fab (patch)
treec58a0f367a3ed998a2a4565a139da543535daef1 /tools/perf/scripts/python/bin/stackcollapse-report
parentcad4a0d6af146e14a82a0f7d43613450dc56ff80 (diff)
drm/xe/uapi: Crystal Reference Clock updates
First of all, let's remove the duplication. But also, let's rename it to remove the word 'frequency' out of it. In general, the first thing people think of frequency is the frequency in which the GTs are operating to execute the GPU instructions. While this frequency here is a crystal reference clock frequency which is the base of everything else, and in this case of this uAPI it is used to calculate a better and precise timestamp. v2: (Suggested by Jose) Remove the engine_cs and keep the GT info one since it might be useful for other SRIOV cases where the engine_cs will be zeroed. So, grabbing from the GT_LIST should be cleaner. v3: Keep comment on put_user() call (José Roberto de Souza) Cc: Matt Roper <[email protected]> Umesh Nerlige Ramappa <[email protected]> Cc: Jose Souza <[email protected]> Signed-off-by: Rodrigo Vivi <[email protected]> Signed-off-by: Francois Dugast <[email protected]> Reviewed-by: José Roberto de Souza <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions