qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>,
	"Anthony Liguori" <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL 4/6] Update documentation for LTTng ust tracing
Date: Wed, 19 Feb 2014 16:45:57 +0100	[thread overview]
Message-ID: <1392824759-7093-5-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1392824759-7093-1-git-send-email-stefanha@redhat.com>

From: Mohamad Gebai <mohamad.gebai@gmail.com>

Signed-off-by: Mohamad Gebai <mohamad.gebai@polymtl.ca>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 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.3

  parent reply	other threads:[~2014-02-19 15:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 15:45 [Qemu-devel] [PULL 0/6] Tracing patches Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 1/6] Fix configure script for LTTng 2.x Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 2/6] Modified the tracetool framework " Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 3/6] Adapt Makefiles to the new LTTng ust interface Stefan Hajnoczi
2014-02-19 15:45 ` Stefan Hajnoczi [this message]
2014-02-19 15:45 ` [Qemu-devel] [PULL 5/6] Add ust generated files to .gitignore Stefan Hajnoczi
2014-02-19 15:45 ` [Qemu-devel] [PULL 6/6] trace-events: Fix typo in "offset" Stefan Hajnoczi
2014-02-19 16:01 ` [Qemu-devel] [PULL 0/6] Tracing patches Lluís Vilanova
2014-02-20 10:24   ` Stefan Hajnoczi
2014-02-21 14:46 ` 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=1392824759-7093-5-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vilanova@ac.upc.edu \
    /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).