[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PULL 01/11] trace: fix simpletrace doc mismerge
From: |
Stefan Hajnoczi |
Subject: |
[PULL 01/11] trace: fix simpletrace doc mismerge |
Date: |
Mon, 1 Feb 2021 15:46:53 +0000 |
The simpletrace documentation section was accidentally split when the
ftrace section was introduced. Move the simpletrace-specific
documentation back into the simpletrace section.
Fixes: e64dd5efb2c6d522a3bc9d096cd49a4e53f0ae10 ("trace: document ftrace
backend")
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-id: 20201216160923.722894-2-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
docs/devel/tracing.txt | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt
index dba43fc7a4..313b8ea4e9 100644
--- a/docs/devel/tracing.txt
+++ b/docs/devel/tracing.txt
@@ -218,6 +218,23 @@ source tree. It may not be as powerful as
platform-specific or third-party
trace backends but it is portable. This is the recommended trace backend
unless you have specific needs for more advanced backends.
+==== Monitor commands ====
+
+* trace-file on|off|flush|set <path>
+ Enable/disable/flush the trace file or set the trace file name.
+
+==== Analyzing trace files ====
+
+The "simple" backend produces binary trace files that can be formatted with the
+simpletrace.py script. The script takes the "trace-events-all" file and the
+binary trace:
+
+ ./scripts/simpletrace.py trace-events-all trace-12345
+
+You must ensure that the same "trace-events-all" file was used to build QEMU,
+otherwise trace event declarations may have changed and output will not be
+consistent.
+
=== Ftrace ===
The "ftrace" backend writes trace data to ftrace marker. This effectively
@@ -246,23 +263,6 @@ NOTE: syslog may squash duplicate consecutive trace events
and apply rate
Restriction: "syslog" backend is restricted to POSIX compliant OS.
-==== Monitor commands ====
-
-* trace-file on|off|flush|set <path>
- Enable/disable/flush the trace file or set the trace file name.
-
-==== Analyzing trace files ====
-
-The "simple" backend produces binary trace files that can be formatted with the
-simpletrace.py script. The script takes the "trace-events-all" file and the
-binary trace:
-
- ./scripts/simpletrace.py trace-events-all trace-12345
-
-You must ensure that the same "trace-events-all" file was used to build QEMU,
-otherwise trace event declarations may have changed and output will not be
-consistent.
-
=== LTTng Userspace Tracer ===
The "ust" backend uses the LTTng Userspace Tracer library. There are no
--
2.29.2
- [PULL 00/11] Tracing patches, Stefan Hajnoczi, 2021/02/01
- [PULL 01/11] trace: fix simpletrace doc mismerge,
Stefan Hajnoczi <=
- [PULL 06/11] trace: add meson custom_target() depend_files for tracetool, Stefan Hajnoczi, 2021/02/01
- [PULL 04/11] tracetool: fix "PRI" macro decoding, Stefan Hajnoczi, 2021/02/01
- [PULL 07/11] error: rename error_with_timestamp to message_with_timestamp, Stefan Hajnoczi, 2021/02/01
- [PULL 08/11] trace: make the 'log' backend timestamp configurable, Stefan Hajnoczi, 2021/02/01
- [PULL 03/11] trace: recommend "log" backend for getting started with tracing, Stefan Hajnoczi, 2021/02/01
- [PULL 02/11] tracing: convert documentation to rST, Stefan Hajnoczi, 2021/02/01
- [PULL 11/11] trace: update docs with meson build information, Stefan Hajnoczi, 2021/02/01
- [PULL 10/11] trace: document how to specify multiple --trace patterns, Stefan Hajnoczi, 2021/02/01