From: Andi Kleen <andi@firstfloor.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: perf.data file format specification draft
Date: Fri, 15 May 2015 15:19:52 +0200 [thread overview]
Message-ID: <20150515131952.GB19417@two.firstfloor.org> (raw)
In-Reply-To: <20150515080600.0651dd6b@gandalf.local.home>
On Fri, May 15, 2015 at 08:06:00AM -0400, Steven Rostedt wrote:
> On Fri, 15 May 2015 01:22:51 -0700
> Stephane Eranian <eranian@google.com> wrote:
>
> > > The quipper C++ parser is available at
> > > https://chromium.googlesource.com/chromiumos/platform/chromiumos-wide-profiling/
> > > Unfortunately this parser tends to be many versions behind and may not be able
> > > to parse data files generated by recent perf.
> > >
> > If you tell me what is missing, I can talk to the ChromeOS people to
> > get the support updated to 4.1.
>
> Please learn to trim your emails. Adding this at the end of a 1000
> lines of quoted text causes everyone else to get finger cramps by
> scrolling through.
I hope you used the time though to actually review the file? @)
How about the missing trace point definitions? I need some help on that.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2015-05-15 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 12:25 perf.data file format specification draft Andi Kleen
2015-05-14 13:11 ` Arnaldo Carvalho de Melo
2015-05-14 13:13 ` Arnaldo Carvalho de Melo
2015-05-18 4:21 ` Namhyung Kim
2015-05-18 16:00 ` Arnaldo Carvalho de Melo
2015-05-15 8:22 ` Stephane Eranian
2015-05-15 12:06 ` Steven Rostedt
2015-05-15 13:19 ` Andi Kleen [this message]
2015-05-15 13:34 ` Steven Rostedt
2015-05-15 13:18 ` Andi Kleen
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=20150515131952.GB19417@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.weaver@maine.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox