fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2026-01-04 02:40:11 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs/perfetto: Be more clear about the role of MESA_GPU_TRACES=perfetto

Browse source 
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/37826>
This commit is contained in:
Emma Anholt 2025-10-10 15:59:15 -07:00 • committed by Marge Bot
parent ed40f0e22a
commit 09793f02bc
1 changed files with 12 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
docs/perfetto.rst
View file

@ -129,17 +129,20 @@ Currently, only EGL and the following drivers have CPU tracepoints.
- VC4
- V3DV
Vulkan data sources
~~~~~~~~~~~~~~~~~~~
Render stage data sources
~~~~~~~~~~~~~~~~~~~~~~~~~
The Vulkan API gives the application control over recording of command
buffers as well as when they are submitted to the hardware. As a
consequence, we need to ensure command buffers are properly
instrumented for the Perfetto driver data sources prior to Perfetto
actually collecting traces.
The render stage data sources are the driver-specific traces of command buffer
execution on the GPU.
This can be achieved by setting the :envvar:`MESA_GPU_TRACES`
environment variable before starting a Vulkan application :
The Vulkan API gives the application control over recording of command buffers
as well as when they are submitted to the hardware, and command buffers can be
recorded once and reused repeatedly. Trace commands are normally only recorded
into a command buffer when a perfetto trace is active. Most applications don't
reuse command buffers, so you'll see traces appear shortly after the trace was
started, but if you have one of the rare applications that reuses command
buffers, you'll need to set the :envvar:`MESA_GPU_TRACES` environment variable
before starting a Vulkan application :
.. code-block:: sh