[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150514131321.GF23588@kernel.org>
Date: Thu, 14 May 2015 10:13:21 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Stephane Eranian <eranian@...gle.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...il.com>, rosted@...radead.org,
adrian.hunter@...el.com, mathieu.desnoyers@...icios.com,
linux-kernel@...r.kernel.org, peterz@...radead.org,
vincent.weaver@...ne.edu
Subject: Re: perf.data file format specification draft
Em Thu, May 14, 2015 at 10:11:29AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, May 14, 2015 at 02:25:17PM +0200, Andi Kleen escreveu:
> > Hi,
> >
> > Since there are more and more consumers I started a description of the
> > on-disk perf.data format. This does not replace the kernel perf event
> > description or the manpage, but describes the parts that perf record
> > adds.
> >
> > So far it is still has some gaps and needs review. Eventually this should
> > become part of the perf documentation.
> >
> > Steven, would be good if you could fill in some details on how trace
> > data works.
>
> I guess that would be Frédéric, and also I think this is a good
> opportunity to remove some stuff that seem to be collected but unused,
> namely a kallsyms copy and maybe something else.
>
> > Adrian, would be good if you could fill in the missing bits for
> > auxtrace/itrace.
> > Everyone else, please review and add missing information.
>
> Thanks for doing this work!
>
> IIRC there is a presentation written by Jiri where parts of this is
> documented, lemme try to find it...
http://tracingsummit.org/w/images/9/98/TracingSummit2014-Perf-CTF.pdf
Look from page 16 on.
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists