diff options
| author | Yaowei Bai | 2018-07-04 05:17:27 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi | 2018-07-19 14:09:04 +0200 |
| commit | db817b8c500a60873eba80cbf047900ae5b32766 (patch) | |
| tree | 65b34642bbcb8a848474c2c2a2d9dcb2ab3a08e0 /docs/devel | |
| parent | Update version for v3.0.0-rc1 release (diff) | |
| download | qemu-db817b8c500a60873eba80cbf047900ae5b32766.tar.gz qemu-db817b8c500a60873eba80cbf047900ae5b32766.tar.xz qemu-db817b8c500a60873eba80cbf047900ae5b32766.zip | |
tracing: Use double-dash spelling for trace option
The '-trace' and '--trace' spellings are only both supported in qemu
binary, while for qemu-nbd or qemu-img only '--trace' spelling is
supported. So for the consistency of trace option invocation, we
should use double-dash spelling in our documentation.
This's also mentioned in
https://wiki.qemu.org/BiteSizedTasks#Consistent_option_usage_in_documentation
.
Signed-off-by: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1530674247-31200-1-git-send-email-baiyaowei@cmss.chinamobile.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'docs/devel')
| -rw-r--r-- | docs/devel/tracing.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/devel/tracing.txt b/docs/devel/tracing.txt index 6f815ecbd7..bc52f12485 100644 --- a/docs/devel/tracing.txt +++ b/docs/devel/tracing.txt @@ -18,7 +18,7 @@ for debugging, profiling, and observing execution. 3. Run the virtual machine to produce a trace file: - qemu -trace events=/tmp/events ... # your normal QEMU invocation + qemu --trace events=/tmp/events ... # your normal QEMU invocation 4. Pretty-print the binary trace file: @@ -157,11 +157,11 @@ The state of events can also be queried and modified through monitor commands: * trace-event NAME on|off Enable/disable a given trace event or a group of events (using wildcards). -The "-trace events=<file>" command line argument can be used to enable the +The "--trace events=<file>" command line argument can be used to enable the events listed in <file> from the very beginning of the program. This file must contain one event name per line. -If a line in the "-trace events=<file>" file begins with a '-', the trace event +If a line in the "--trace events=<file>" file begins with a '-', the trace event will be disabled instead of enabled. This is useful when a wildcard was used to enable an entire family of events but one noisy event needs to be disabled. |