motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-08-14 21:52:18 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

trace: fix simpletrace doc mismerge

Browse source 
The simpletrace documentation section was accidentally split when the
ftrace section was introduced. Move the simpletrace-specific
documentation back into the simpletrace section.

Fixes: e64dd5efb2 ("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>
This commit is contained in:
Stefan Hajnoczi 2020-12-16 16:09:21 +00:00
parent 74208cd252
commit c72e3e4842
1 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

34
docs/devel/tracing.txt
View file

@ -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 trace backends but it is portable. This is the recommended trace backend
unless you have specific needs for more advanced backends. 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 === === Ftrace ===
The "ftrace" backend writes trace data to ftrace marker. This effectively 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. 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 === === LTTng Userspace Tracer ===
The "ust" backend uses the LTTng Userspace Tracer library. There are no The "ust" backend uses the LTTng Userspace Tracer library. There are no