mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-21 13:00:22 +01:00
When CPU clock is the same with the authoritative trace clock (normally default to CLOCK_BOOTTIME), perfetto drops the non-monotonic snapshots to ensure validity of the global source clock in the resolution graph. When they are different, the clocks are marked invalid and the rest of the clock syncs will fail during trace processing. There's no central daemon emitting consistent snapshots for synchronization between CPU and GPU clocks on behalf of renderstages and counters producers. The sequence-scoped clock (64 <= ID < 128) is unique per producer + writer pair within the tracing session. So we can use sequence-scoped clock for gpu clock whenever applicable, and fallback to use global clock for dynamic minor allocated >= 192. Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37425> |
||
|---|---|---|
| .. | ||
| .clang-format | ||
| intel_driver_ds.cc | ||
| intel_driver_ds.h | ||
| intel_pps_driver.cc | ||
| intel_pps_driver.h | ||
| intel_pps_perf.cc | ||
| intel_pps_perf.h | ||
| intel_pps_priv.h | ||
| intel_tracepoints.py | ||
| meson.build | ||