From: Mohamad Gebai <mohamad.gebai@gmail.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, Mohamad Gebai <mohamad.gebai@polymtl.ca>,
alex.bennee@linaro.org
Subject: [Qemu-devel] [PATCH v6 4/5] Update documentation for LTTng ust tracing
Date: Wed, 29 Jan 2014 22:47:57 -0500 [thread overview]
Message-ID: <1391053678-25398-5-git-send-email-mohamad.gebai@polymtl.ca> (raw)
In-Reply-To: <1391053678-25398-1-git-send-email-mohamad.gebai@polymtl.ca>
Signed-off-by: Mohamad Gebai <mohamad.gebai@polymtl.ca>
---
docs/tracing.txt | 36 ++++++++++++++++++++++++++++++++++++
1 file changed, 36 insertions(+)
diff --git a/docs/tracing.txt b/docs/tracing.txt
index bfc261b..bf2e15c 100644
--- a/docs/tracing.txt
+++ b/docs/tracing.txt
@@ -214,6 +214,42 @@ The "ust" backend uses the LTTng Userspace Tracer library. There are no
monitor commands built into QEMU, instead UST utilities should be used to list,
enable/disable, and dump traces.
+Package lttng-tools is required for userspace tracing. You must ensure that the
+current user belongs to the "tracing" group, or manually launch the
+lttng-sessiond daemon for the current user prior to running any instance of
+QEMU.
+
+While running an instrumented QEMU, LTTng should be able to list all available
+events:
+
+ lttng list -u
+
+Create tracing session:
+
+ lttng create mysession
+
+Enable events:
+
+ lttng enable-event qemu:g_malloc -u
+
+Where the events can either be a comma-separated list of events, or "-a" to
+enable all tracepoint events. Start and stop tracing as needed:
+
+ lttng start
+ lttng stop
+
+View the trace:
+
+ lttng view
+
+Destroy tracing session:
+
+ lttng destroy
+
+Babeltrace can be used at any later time to view the trace:
+
+ babeltrace $HOME/lttng-traces/mysession-<date>-<time>
+
=== SystemTap ===
The "dtrace" backend uses DTrace sdt probes but has only been tested with
--
1.8.5.2
next prev parent reply other threads:[~2014-01-30 3:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 3:47 [Qemu-devel] [PATCH v6 0/5] Fix UST backend for LTTng 2.x Mohamad Gebai
2014-01-30 3:47 ` [Qemu-devel] [PATCH v6 1/5] Fix configure script " Mohamad Gebai
2014-01-30 3:47 ` [Qemu-devel] [PATCH v6 2/5] Modified the tracetool framework " Mohamad Gebai
2014-01-30 3:47 ` [Qemu-devel] [PATCH v6 3/5] Adapt Makefiles to the new LTTng ust interface Mohamad Gebai
2014-01-30 3:47 ` Mohamad Gebai [this message]
2014-01-30 9:55 ` [Qemu-devel] [PATCH v6 4/5] Update documentation for LTTng ust tracing Alex Bennée
2014-01-30 3:47 ` [Qemu-devel] [PATCH v6 5/5] Add ust generated files to .gitignore Mohamad Gebai
2014-01-30 14:02 ` [Qemu-devel] [PATCH v6 0/5] Fix UST backend for LTTng 2.x Stefan Hajnoczi
2014-01-30 15:59 ` Mohamad Gebai
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=1391053678-25398-5-git-send-email-mohamad.gebai@polymtl.ca \
--to=mohamad.gebai@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=mohamad.gebai@polymtl.ca \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).