All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: diamon-discuss@lists.linuxfoundation.org,
	dominique.toupin@ericsson.com, Jiri Olsa <jolsa@redhat.com>
Cc: Xinwei Hu <huxinwei@huawei.com>, genghui 00204690 <hui.geng@huawei.com>
Subject: [diamon-discuss] Diamon CTF Roadmap?
Date: Tue, 25 Nov 2014 21:03:44 +0800	[thread overview]
Message-ID: <54747E30.6000509@huawei.com> (raw)

Hi everyone,

Looks like my post will be the second thread in this list. That's great.

I'll be the technical contact person representing Huawei for Diamon.
I'm glad to work with this new workgroup to create "de-facto, widely
used open source trace technologies".

Beyond sharing new ideas and technologies, our main concern on Diamon
now are CTF tracing format and related things for analysing traces from
different sources in a unified manner. I have read Jiri Olsa's slides in
TracingSummit 2014, and also begin to read his code in
https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git. However,
it looks like that there's only a trace generating tool is under
developing. What about upper trace parsing and analysing tools? Is there
any roadmap on it? How can we participate in the project?

Thanks.


             reply	other threads:[~2014-11-25 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 13:03 Wang Nan [this message]
2014-11-25 13:42 ` [diamon-discuss] Diamon CTF Roadmap? Dominique Toupin
2014-11-26  2:08   ` Wang Nan
2014-11-26 19:43     ` Dominique Toupin
2014-11-27  1:51       ` Wang Nan
2014-11-27 12:41         ` Dominique Toupin

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=54747E30.6000509@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=dominique.toupin@ericsson.com \
    --cc=hui.geng@huawei.com \
    --cc=huxinwei@huawei.com \
    --cc=jolsa@redhat.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.