diff options
| author | Stefan Hajnoczi | 2020-12-16 17:09:21 +0100 |
|---|---|---|
| committer | Stefan Hajnoczi | 2021-02-01 11:50:54 +0100 |
| commit | c72e3e48420864af6c688ae6b9bc6f159c916598 (patch) | |
| tree | 30380ee8bfb9048127b1a785429eadd71aeb3e38 /docs/devel | |
| parent | Merge remote-tracking branch 'remotes/berrange-gitlab/tags/misc-fixes-pull-re... (diff) | |
| download | qemu-c72e3e48420864af6c688ae6b9bc6f159c916598.tar.gz qemu-c72e3e48420864af6c688ae6b9bc6f159c916598.tar.xz qemu-c72e3e48420864af6c688ae6b9bc6f159c916598.zip | |
trace: fix simpletrace doc mismerge
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>
Diffstat (limited to 'docs/devel')
| -rw-r--r-- | docs/devel/tracing.txt | 34 |
1 files 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 |