All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Montplaisir <alexmonthy@voxpopuli.im>
To: Wang Nan <wangnan0@huawei.com>
Cc: "diamon-discuss@lists.linuxfoundation.org"
	<diamon-discuss@lists.linuxfoundation.org>,
	lttng-dev@lists.lttng.org,
	tracecompass developer discussions <tracecompass-dev@eclipse.org>
Subject: Re: [diamon-discuss] My experience on perf, CTF and TraceCompass, and some suggection.
Date: Fri, 23 Jan 2015 15:12:27 -0500	[thread overview]
Message-ID: <54C2AB2B.6000105@voxpopuli.im> (raw)
In-Reply-To: <54C215D6.1030804@huawei.com>


On 01/23/2015 04:35 AM, Wang Nan wrote:
> [...] I prefer to use:
>
>   # perf record -a -e sched:* -e syscalls:* sleep 1
>
> However there are some bugs and I have to make some patches. They are
> posted and being disscussed currently, those bugs are still exist
> upstream.

Hmm, I can confirm this problem, when trying to convert a trace taken 
with these events enabled, I get the following error:

Failed to add field 'nr
Failed to add event 'syscalls:sys_enter_io_submit'.

Good to know it's being looked at!


But when you say:

> TraceCompass doesn't recognize syscall:* tracepoints as CPU status
> changing point. I have to also catch raw_syscall:*, and which doubles
> the number of samples.

I assume this was that with your patches applied, so that you could take 
a trace of the syscall:* tracepoints?

Do you have a link to those patches somewhere? Or just let us know when 
it gets integrated upstream. I was trying to update the analysis in 
Trace Compass to handle syscall:* too, but we can't really do it without 
knowing how it will look like in CTF format ;)


Cheers,
Alexandre


  parent reply	other threads:[~2015-01-23 20:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  9:35 [diamon-discuss] My experience on perf, CTF and TraceCompass, and some suggection Wang Nan
2015-01-23 16:30 ` Alexandre Montplaisir
2015-01-23 16:56   ` Geneviève Bastien
2015-01-23 16:56   ` [diamon-discuss] [lttng-dev] " Geneviève Bastien
2015-01-31  7:14   ` [diamon-discuss] " Wang Nan
2015-02-04 20:24     ` Alexandre Montplaisir
2015-02-04 20:24     ` Alexandre Montplaisir
2015-02-07  3:13       ` Wang Nan
2015-02-07  3:13       ` Wang Nan
2015-02-07  5:14         ` Alexandre Montplaisir
2015-02-07  5:14         ` Alexandre Montplaisir
2015-02-07  7:25           ` Wang Nan
2015-02-07  7:25           ` Wang Nan
2015-02-09 20:13             ` Alexandre Montplaisir
2015-02-10  4:55               ` Wang Nan
2015-02-10  8:02                 ` Alexandre Montplaisir
2015-02-10  8:02                 ` Alexandre Montplaisir
2015-02-10  4:55               ` Wang Nan
2015-02-09 20:13             ` Alexandre Montplaisir
2015-02-07 13:22     ` Mathieu Desnoyers
2015-02-07 13:22     ` Mathieu Desnoyers
2015-01-31  7:14   ` Wang Nan
2015-01-23 16:30 ` Alexandre Montplaisir
2015-01-23 20:12 ` Alexandre Montplaisir [this message]
2015-01-26  4:08   ` Wang Nan
2015-01-26  4:08   ` Wang Nan
2015-01-23 20:12 ` Alexandre Montplaisir
2015-01-26 16:25 ` Jérémie Galarneau
2015-01-26 16:25 ` Jérémie Galarneau
2015-01-27  0:54   ` Wang Nan
2015-01-27  5:31     ` Jérémie Galarneau
2015-01-27  5:31     ` Jérémie Galarneau
2015-01-27  6:31       ` Wang Nan
2015-01-27  6:31       ` Wang Nan
2015-01-27  0:54   ` Wang Nan

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=54C2AB2B.6000105@voxpopuli.im \
    --to=alexmonthy@voxpopuli.im \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=tracecompass-dev@eclipse.org \
    --cc=wangnan0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.