All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: Dominique Toupin <dominique.toupin@ericsson.com>,
	"diamon-discuss@lists.linuxfoundation.org"
	<diamon-discuss@lists.linuxfoundation.org>,
	Jiri Olsa <jolsa@redhat.com>
Cc: Xinwei Hu <huxinwei@huawei.com>, genghui 00204690 <hui.geng@huawei.com>
Subject: Re: [diamon-discuss] Diamon CTF Roadmap?
Date: Wed, 26 Nov 2014 10:08:28 +0800	[thread overview]
Message-ID: <5475361C.50604@huawei.com> (raw)
In-Reply-To: <AA1354619DD14B469E3D986393D885DC1BA22AE4@eusaamb103.ericsson.se>

On 2014/11/25 21:42, Dominique Toupin wrote:
> Hi Nan,
> 
> Many tools are able to handle CTF today, e.g.:
> - GDB Tracepoint https://sourceware.org/gdb/onlinedocs/gdb/Trace-Files.html#Trace-Files
> - LTTng kernel and LTTng user space C/C++, Java, Python, etc. https://lttng.org/download
> - babel trace, http://lttng.org/viewers/ 
> - Trace Compass http://projects.eclipse.org/projects/tools.tracecompass 
> - CTF tracer for bare metal https://github.com/efficios/barectf/blob/master/README.md
> 
> You will also find many converter to CTF, e.g. NEXUS HW Trace, perf, 
> And I am most likely missing a few.
> 
> If you can provide a description of your needs it would help to give you more info related to your use case.
> e.g. is it more related to cloud, embedded data base, real time, or do you have a specific view or analysis you want to see in the trace viewer, etc.
> 

Our use cases are diverse, both embedded and server scene have requirements on profiling,
and methodologies are also different.

We have two starting points now:

1. On ARM (32/64) platform, extracing information (instruction footprints) from CoreSight
   using perf and use CTF as trace format, to make it possible to analysis with trace from
   upper layer. Intel has similar hardware too, but currently only on specification.

2. On server field, providing some interactive, graphical user interfaces for some generic
   problems. Android's SysTrace is a good example. However, our the real goal is to create
   a tool for dealing with problems not so generic. Profiling using a language like SQL maybe,
   like Splunk, to synthesize traces from different layers and components. So the underlying
   traces are better to be in a uniform format.

We also concern the upstreaming plan about kernel stuffs in DiaMon.

> Thanks for the second post!
> 
> Dominique
> 
> -----Original Message-----
> From: Wang Nan [mailto:wangnan0@huawei.com] 
> Sent: November-25-14 8:04 AM
> To: diamon-discuss@lists.linuxfoundation.org; Dominique Toupin; Jiri Olsa
> Cc: genghui 00204690; Xinwei Hu
> Subject: Diamon CTF Roadmap?
> 
> 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-26  2:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 13:03 [diamon-discuss] Diamon CTF Roadmap? Wang Nan
2014-11-25 13:42 ` Dominique Toupin
2014-11-26  2:08   ` Wang Nan [this message]
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=5475361C.50604@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.