From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:32904)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mohamad.gebai@polymtl.ca>) id 1VW79b-0003or-UR
	for qemu-devel@nongnu.org; Tue, 15 Oct 2013 12:07:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mohamad.gebai@polymtl.ca>) id 1VW79U-0001nm-Lv
	for qemu-devel@nongnu.org; Tue, 15 Oct 2013 12:07:27 -0400
Received: from smtp.polymtl.ca ([132.207.4.11]:36467)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mohamad.gebai@polymtl.ca>) id 1VW79U-0001ng-G7
	for qemu-devel@nongnu.org; Tue, 15 Oct 2013 12:07:20 -0400
Message-ID: <525D6832.9060703@polymtl.ca>
Date: Tue, 15 Oct 2013 12:07:14 -0400
From: Mohamad Gebai <mohamad.gebai@polymtl.ca>
MIME-Version: 1.0
References: <1381775755-8421-1-git-send-email-mohamad.gebai@polymtl.ca>
	<1381775755-8421-5-git-send-email-mohamad.gebai@polymtl.ca>
	<p1zjqaye38.fsf@linaro.org>
In-Reply-To: <p1zjqaye38.fsf@linaro.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC PATCH v3 4/5] Update documentation for LTTng
	ust tracing
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?UTF-8?B?QWxleCBCZW5uw6ll?= <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Mohamad Gebai <mohamad.gebai@gmail.com>


> 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