diff options
| -rw-r--r-- | docs/perfetto.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/perfetto.rst b/docs/perfetto.rst index 72290a8ad94..5981ffcdc10 100644 --- a/docs/perfetto.rst +++ b/docs/perfetto.rst @@ -14,7 +14,7 @@ data-sources for things like: As well as various domain specific producers. -The mesa perfetto support adds additional producers, to allow for visualizing +The mesa Perfetto support adds additional producers, to allow for visualizing GPU performance (frequency, utilization, performance counters, etc) on the same timeline, to better understand and tune/debug system level performance: @@ -47,9 +47,9 @@ The exact supported features vary per driver: Run --- -To capture a trace with perfetto you need to take the following steps: +To capture a trace with Perfetto you need to take the following steps: -1. Build perfetto from sources available at ``subprojects/perfetto`` following +1. Build Perfetto from sources available at ``subprojects/perfetto`` following `this guide <https://perfetto.dev/docs/quickstart/linux-tracing>`__. 2. Create a `trace config <https://perfetto.dev/#/trace-config.md>`__, which is @@ -118,7 +118,7 @@ Vulkan 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 +instrumented for the Perfetto driver data sources prior to Perfetto actually collecting traces. This can be achieved by setting the ``GPU_TRACE_INSTRUMENT`` |