qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohamad Gebai <mohamad.gebai@polymtl.ca>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Mohamad Gebai <mohamad.gebai@gmail.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 4/5] Update documentation for LTTng ust tracing
Date: Tue, 15 Oct 2013 12:07:14 -0400	[thread overview]
Message-ID: <525D6832.9060703@polymtl.ca> (raw)
In-Reply-To: <p1zjqaye38.fsf@linaro.org>


> Running this gives me:
>
> <quote>
> UST events:
> -------------
> None
> </quote>
>
> Before or after running qemu. What is the mechanism lttng expects to
> find out all these events?

Either the user should belong the group "tracing", or launch the 
lttng-sessiond daemon (lttng-sessiond -d).

>
>> +
>> +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>
>> +
> The rest of this looks OK and worked on my system.
>
>>   === SystemTap ===
>>   
>>   The "dtrace" backend uses DTrace sdt probes but has only been tested with
>
Thanks!
Mohamad

  reply	other threads:[~2013-10-15 16:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 18:35 [Qemu-devel] [RFC PATCH v3 0/5] Fix UST backend for LTTng 2.x Mohamad Gebai
2013-10-14 18:35 ` [Qemu-devel] [RFC PATCH v3 1/5] Fix configure script " Mohamad Gebai
2013-10-16 12:06   ` Alex Bennée
2013-10-14 18:35 ` [Qemu-devel] [RFC PATCH v3 2/5] Modified the tracetool framework " Mohamad Gebai
2013-10-16 12:06   ` Alex Bennée
2013-10-14 18:35 ` [Qemu-devel] [RFC PATCH v3 3/5] Adapt Makefiles to the new LTTng ust interface Mohamad Gebai
2013-10-16 12:08   ` Alex Bennée
2013-10-17  1:04     ` Mohamad Gebai
2013-10-14 18:35 ` [Qemu-devel] [RFC PATCH v3 4/5] Update documentation for LTTng ust tracing Mohamad Gebai
2013-10-15 11:21   ` Alex Bennée
2013-10-15 16:07     ` Mohamad Gebai [this message]
2013-10-16 12:05       ` Alex Bennée
2013-10-17  1:02         ` Mohamad Gebai
2013-10-17  9:20           ` Alex Bennée
2013-10-18  6:38             ` Mohamad Gebai
2013-10-14 18:35 ` [Qemu-devel] [RFC PATCH v3 5/5] Add ust generated files to .gitignore Mohamad Gebai
2013-10-16 12:08   ` Alex Bennée

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=525D6832.9060703@polymtl.ca \
    --to=mohamad.gebai@polymtl.ca \
    --cc=alex.bennee@linaro.org \
    --cc=mohamad.gebai@gmail.com \
    --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).