From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Steven Rostedt <rostedt@goodmis.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:18:35 +0200 [thread overview]
Message-ID: <20150515131834.GA19417@two.firstfloor.org> (raw)
In-Reply-To: <CABPqkBQLofuX=HkAj9b1zGob139hGSU3GAGnYL7yrXLWn+e52g@mail.gmail.com>
> > 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.
they just need to try it and fix it until it works. And then retry
every three months when a new perf comes out.
Part of the problem is that programing style with excessive asserting.
If you add that many asserts you also need to keep up with the input data.
It's the opposite of "be liberal what you accept"
Right now it still bombs out for various records that newer perf adds.
I send some patches for autofdo to hack around that, but they were not quite enough:
https://gcc.gnu.org/ml/gcc/2015-04/msg00271.html
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2015-05-15 13:18 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
2015-05-15 13:34 ` Steven Rostedt
2015-05-15 13:18 ` Andi Kleen [this message]
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=20150515131834.GA19417@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