From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Omar Awile <omar.awile@cern.ch>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: reading PMU counts with perf leader sampling and perf script
Date: Tue, 20 Sep 2016 13:16:25 -0700 [thread overview]
Message-ID: <8737kupbs6.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <20160920191953.GF4973@kernel.org> (Arnaldo Carvalho de Melo's message of "Tue, 20 Sep 2016 16:19:53 -0300")
Arnaldo Carvalho de Melo <acme@kernel.org> writes:
> Em Tue, Sep 20, 2016 at 03:19:47PM +0000, Omar Awile escreveu:
>> Hi Arnaldo,
>
>> Ah that’s pretty neat. I will try it out. I found perf script really
>> useful to generate properly formatted CSV (after I finally understood
>> how to correctly use it). This might be something worth adding as a
>> feature across all perf tools (stat, report, script). I know that some
>> of the tools can print something kind of CSV, but it’s still just
>> kind-of and not properly formatted, which makes parsing and processing
>
> So, can you provide specific examples of things you think are wrong so
> that we can see if something can be made to improve it?
The main problem is that commas are not quoted (or rather not put into
""), and cpu events have a lot of commas. So -x, tends to output
invalid CSV.
However it generally works well enough with -x; and most CSV tools
can handle that too.
-Andi
prev parent reply other threads:[~2016-09-20 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:48 reading PMU counts with perf leader sampling and perf script Omar Awile
2016-09-11 3:21 ` Andi Kleen
2016-09-20 14:33 ` Omar Awile
2016-09-12 20:04 ` Arnaldo Carvalho de Melo
[not found] ` <etPan.57e15392.6894e226.675c@cern.ch>
2016-09-20 19:19 ` Arnaldo Carvalho de Melo
2016-09-20 20:16 ` 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=8737kupbs6.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=omar.awile@cern.ch \
/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.