qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Mohamad Gebai <mohamad.gebai@polymtl.ca>
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: Thu, 17 Oct 2013 10:20:02 +0100	[thread overview]
Message-ID: <p1iowwtfst.fsf@linaro.org> (raw)
In-Reply-To: <525F3709.7070506@polymtl.ca>


mohamad.gebai@polymtl.ca writes:

> On 13-10-16 08:05 AM, Alex Bennée wrote:
>>>> 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).
>> <snip>
>>
>> Hmm I've done both and I get nothing still. I can enable all tracepoints
>> though. This could just be a Ubuntu weirdness thing though.
>
> That's weird. I did test it on a clean Ubuntu Precise (in a VM) and I 
> didn't have any problem after either one of these steps. Can you please 
> make sure that the user belongs to the "tracing" group and that the 
> lttng-sessiond daemon is running before running any instance of Qemu. 
> Also, Qemu should be running for LTTng to be able to list the events.

Ahh that was it. I suggest you change the wording from:

"Package lttng-tools is required for userspace tracing. After running Qemu, LTTng
should be able to list all available events:"

to

"Package lttng-tools is required for userspace tracing. While running
and instrumented Qemu, LTTng should be able to list all available events:"

> Does lttng enable-event -a -u/start/stop/view show any event?

Yes, as I said the rest worked fine. With that minor wording fix I'm happy.

Thanks for getting this back into shape :-)

-- 
Alex Bennée

  reply	other threads:[~2013-10-17  9:20 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
2013-10-16 12:05       ` Alex Bennée
2013-10-17  1:02         ` Mohamad Gebai
2013-10-17  9:20           ` Alex Bennée [this message]
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=p1iowwtfst.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=mohamad.gebai@gmail.com \
    --cc=mohamad.gebai@polymtl.ca \
    --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).