Date: Thu, 14 May 2015 10:11:29 -0300
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: eranian@google.com, jolsa@kernel.org, namhyung@kernel.org,
        rostedt@goodmis.org, adrian.hunter@intel.com,
        mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
        peterz@infradead.org, vincent.weaver@maine.edu
Subject: Re: perf.data file format specification draft
Message-ID: <20150514131129.GE23588@kernel.org>
References: <20150514122517.GZ2366@two.firstfloor.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20150514122517.GZ2366@two.firstfloor.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1226
Lines: 33

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...

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/