docs: update the usage example of "dtrace" backend in tracing.txt
PATCH 1/1 docs: update the usage example of "dtrace" backend in tracing.txt
The usage example of dtrace is quite ancient, We have tracetool.py with different parameters instead of the original tracetool shell script for a long time, So update the old information.
Signed-off-by Lin Ma <[email protected]>
--- docs/tracing.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
docs/tracing.txt +5 -5
@@ -258,11 +258,11 @@ is generated to make use in scripts more convenient. This step can also be performed manually after a build in order to change the binary name in the .stp probes: - scripts/tracetool --dtrace --stap \ - --binary path/to/qemu-binary \ - --target-type system \ - --target-name x86_64 \ - <trace-events >qemu.stp + scripts/tracetool.py --backends=dtrace --format=stap \ + --binary path/to/qemu-binary \ + --target-type system \ + --target-name x86_64 \ + <trace-events >qemu.stp == Trace event properties ==
Signature · 1 line
2.1.4
Quoted 8 lines · Lin Ma
The usage example of dtrace is quite ancient, We have
tracetool.pywith different parameters instead of the original tracetool shell script for a long time, So update the old information.Signed-off-by Lin Ma <[email protected]>--- docs/tracing.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
Reviewed-by Ján Tomko <[email protected]>
Stefan Hajnoczi
AppliedQuoted 8 lines · Lin Ma
The usage example of dtrace is quite ancient, We have
tracetool.pywith different parameters instead of the original tracetool shell script for a long time, So update the old information.Signed-off-by Lin Ma <[email protected]>--- docs/tracing.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan