summaryrefslogtreecommitdiff
path: root/doc/develop
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2024-12-31 19:00:54 -0600
committerTom Rini <trini@konsulko.com>2025-01-01 10:40:33 -0600
commit2eb74974de5204835e81b81098dab1591fd99df5 (patch)
tree76b6ffcd649422cd0755efa6cb1e831eaff9597f /doc/develop
parent788b4609dbbbf1e058836b42967e58ffcbdc3bb1 (diff)
parentedef0916668631b4fce956a9cfac252ffb2c0a9c (diff)
Merge patch series "Add 'trace wipe'"
Jerome Forissier <jerome.forissier@linaro.org> says: This short series adds the 'trace wipe' command which clears the trace buffer, allowing to re-start a capture from scratch. Link: https://lore.kernel.org/r/cover.1734093566.git.jerome.forissier@linaro.org
Diffstat (limited to 'doc/develop')
-rw-r--r--doc/develop/trace.rst11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/develop/trace.rst b/doc/develop/trace.rst
index 546862020b1..d3c8628d124 100644
--- a/doc/develop/trace.rst
+++ b/doc/develop/trace.rst
@@ -163,6 +163,17 @@ you will see the time taken by each function shown against its exit record.
u-boot-1 [000] 3.116466: funcgraph_entry: 0.063 us | memset();
u-boot-1 [000] 3.116539: funcgraph_exit: 0.143 us | }
+The `trace wipe` command may be used to clear the trace buffer. It leaves
+tracing in its current enable state. This command is convenient when tracing a
+single command, for example:
+
+.. code-block:: console
+
+ => trace pause; trace wipe
+ => trace resume; dhcp; trace pause
+ => trace stats
+ ...
+
Flame graph
-----------