mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-16 00:40:32 +01:00
a871eabced
Perfetto is allowed to choose it's own default clock, and before this we just assumed the presentation times reported by the compositor are the same as perfetto's internal clock, which is not always the case. I got a nasty trace where all the wayland presents were in the wrong location. This fixes that by asking the compositor which clock it uses, then passing that along to perfetto.
A workaround for my compositor was setting use_monotonic_clock=true in the perfetto config, as my compositor (and I suspect most others) use the monotonic clock for presentation timestamps. However, asking the compositor is definitely the most correct solution.
I added a clock param to `MESA_TRACE_TIMESTAMP_{BEGIN,END}`, as it's only use that I could see was in wsi_common_wayland, and in general it seems good to be careful about which clock tracing timestamps come from.
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31779>
|
||
|---|---|---|
| .. | ||
| device-select-layer | ||
| overlay-layer | ||
| registry | ||
| runtime | ||
| screenshot-layer | ||
| util | ||
| wsi | ||
| meson.build | ||
| vulkan-android.sym | ||
| vulkan-icd-android-symbols.txt | ||
| vulkan-icd-symbols.txt | ||
| vulkan.sym | ||
| vulkan_api.def.in | ||