Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: David_Ke@compal.com (David_Ke@compal.com)
Subject: [lttng-dev] great to read  your presention
Date: Tue, 11 Feb 2014 16:54:23 +0800	[thread overview]
Message-ID: <E9A0D02B1D74EE4DBF9C09777345E107038FDA7C@tpeexg06.compal.com> (raw)
In-Reply-To: <52F8ED5C.5050106@versatic.net>

Hi Genevi?ve,

Cool~
Hope to see it soon.

Thanks,

David

-----Original Message-----
From: Genevi?ve Bastien [mailto:gbastien+lttng@versatic.net] 
Sent: Monday, February 10, 2014 11:17 PM
To: Ke. David (TPE); alexmonthy at voxpopuli.im
Cc: lttng-dev at lists.lttng.org
Subject: Re: [lttng-dev] great to read your presention

Hi David,

As Alex said, the CPU usage is still a work in progress. The data is
available now, but we are working on a view to better show it. It should all
be available in master in the coming weeks.

As for the wait chain, you may be interested in the critical path analysis on
LTTng kernel traces. This feature will make it slowly into master, but in the
meantime, you can try it in our experimental version of the tracing RCP
available here: 
http://secretaire.dorsal.polymtl.ca/~gbastien/TracingRCP/

You can get the critical path of a process by selecting it in the control
flow view (with the critical path view open).

Cheers,
Genevi?ve


On 02/09/2014 10:49 PM, David_Ke at compal.com wrote:
> Thanks, Alexandre,
>
> Good to hear that.
> Hope to get that soon.
> By the way, some feature to suggest for the utility~ The control flow 
> is aim to analyze the "long wait time" issue for that process, IMHO, 
> If it can display the "wait chain" as well as the call stack for each 
> scheduled thread ,it will be awesome...
>
> Thanks,
>
> David
>
> ----Original Message-----
> From: Alexandre Montplaisir [mailto:alexmonthy@voxpopuli.im]
> Sent: Saturday, February 08, 2014 6:39 AM
> To: Ke. David (TPE)
> Cc: lttng-dev at lists.lttng.org; Genevieve Bastien
> Subject: Re: [lttng-dev] great to read your presention
>
> Hi,
>
> The CPU usage view is still a work-in-progress, but it should be ready 
> in a few weeks. We have a bit of infrastructure work to do first.
>
> CC'ing Genevieve, she can probably give us more details about its state.
>
> Cheers,
> Alexandre
>
>
>
> On 14-02-04 08:55 PM, David_Ke at compal.com wrote:
>> Hi Yannick,
>>
>>   
>>
>> Great to read your deck and it is really a good presentation, from 
>> that ,I know more about awesome features of Lttng.
>>
>>   
>>
>> I was a SR. DEV of MSFT Windows team and was responsible for Xperf 
>> and ADK portion in the past, Lttng did catch my eye much more than 
>> other utilities (for example perf and oprefile...etc.)
>>
>>   
>>
>> I download Lttng sample
>> trace(http://lttng.org/files/samples/sample-ctf-trace-20120412.tar.bz
>> 2
>> )as
>> well as the RCP version trace viewer( 
>> http://secretaire.dorsal.polymtl.ca/~alexmont/tracing-rcp/)but can't 
>> find the CPU usage tab in the viewer.
>>
>>   
>>
>> Is the feature still under development? Where can I got it and have a try?
>>
>>   
>>
>> Thanks,
>>
>>   
>>
>> David Ke
>>
>>
>>
>> =====================================================================
>> = 
>> =====================================================================
>> = ==================== This message may contain information which is 
>> private, privileged or confidential of Compal Electronics, Inc.  If 
>> you are
> not the intended recipient of this message, please notify the sender 
> and destroy/delete the message. Any review, retransmission, 
> dissemination or other use of, or taking of any action in reliance 
> upon this information, by persons or entities other than the intended
recipient is prohibited.
>> =====================================================================
>> = 
>> =====================================================================
>> =
>> ====================
>>
>>




      reply	other threads:[~2014-02-11  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  1:55 David_Ke
2014-02-07 22:38 ` Alexandre Montplaisir
2014-02-10  3:49   ` David_Ke
2014-02-10 15:16     ` Geneviève Bastien
2014-02-11  8:54       ` David_Ke [this message]

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=E9A0D02B1D74EE4DBF9C09777345E107038FDA7C@tpeexg06.compal.com \
    --to=david_ke@compal.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