trace: docs: add trace file description
authorChen Fan <chen.fan.fnst@cn.fujitsu.com>
Fri, 11 Jul 2014 03:24:37 +0000 (11:24 +0800)
committerStefan Hajnoczi <stefanha@redhat.com>
Fri, 26 Sep 2014 08:34:38 +0000 (09:34 +0100)
When user used the trace print command from docs/tracing.txt:
  ./scripts/simpletrace.py trace-events trace-*

the user maybe be misled by the "trace-*", because if user
directly copy the comand line to run, there alway print the
bored message:
"usage: ./scripts/simpletrace.py <trace-events> <trace-file>"

then we should describe that the "trace-*" represented.

Signed-off-by: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
docs/tracing.txt

index 2e035a5b3c1d900ac9cf5dcad1f5c630dce77baa..7d389263940d09531a882d8157256daa2475b5b8 100644 (file)
@@ -23,7 +23,7 @@ for debugging, profiling, and observing execution.
 
 4. Pretty-print the binary trace file:
 
-    ./scripts/simpletrace.py trace-events trace-*
+    ./scripts/simpletrace.py trace-events trace-* # Override * with QEMU <pid>
 
 == Trace events ==