From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>, Lin Ma <lma@suse.com>
Subject: [Qemu-devel] [PULL 1/2] docs: update the usage example of "dtrace" backend in tracing.txt
Date: Fri, 9 Oct 2015 10:15:18 +0100 [thread overview]
Message-ID: <1444382119-24700-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1444382119-24700-1-git-send-email-stefanha@redhat.com>
From: Lin Ma <lma@suse.com>
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 <lma@suse.com>
Message-id: 1441954730-17341-1-git-send-email-lma@suse.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
docs/tracing.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/tracing.txt b/docs/tracing.txt
index 7117c5e..3853a6a 100644
--- a/docs/tracing.txt
+++ b/docs/tracing.txt
@@ -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 ==
--
2.4.3
next prev parent reply other threads:[~2015-10-09 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 9:15 [Qemu-devel] [PULL 0/2] Tracing patches Stefan Hajnoczi
2015-10-09 9:15 ` Stefan Hajnoczi [this message]
2015-10-09 9:15 ` [Qemu-devel] [PULL 2/2] trace: remove malloc tracing Stefan Hajnoczi
2015-10-09 12:19 ` [Qemu-devel] [PULL 0/2] Tracing patches Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1444382119-24700-2-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=lma@suse.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).