From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools: Make perf stat -I ... CSV output flat
Date: Wed, 13 Mar 2013 12:49:29 -0300 [thread overview]
Message-ID: <20130313154928.GA15763@infradead.org> (raw)
In-Reply-To: <CABPqkBT06EVjuy1ew1Z+vrGMf0p+mH19-M71xzTGVyZTtcaLUA@mail.gmail.com>
Em Wed, Mar 13, 2013 at 02:19:05PM +0100, Stephane Eranian escreveu:
> On Thu, Mar 7, 2013 at 3:43 AM, Andi Kleen <andi@firstfloor.org> wrote:
> >
> > + if (interval && csv_output) {
> > + fprintf(output, "time,,");
>
> Don't quite understand the point of the ,,. By definition this
> extension is used for automatic
> post-processing. I cannot find a good justification for the
> double-comma, except for making
Yeah, that and the trailing comma as well, don't think they are needed.
> reading the output easy. But that's contradictory with the gnuplot goal.
> Also you need to add a # in front of this line to mark the line so it
> can be discarded (as comment)
> by any post-processing parser (such as gnuplot).
>
>
> Also I think something needs to be improved for the non-aggregated output
> in system-wide mode:
>
> $ perf stat -I 10000 -x, -a -A -e cycles,instructions sleep 5
>
> Don't you want events also grouped by CPU?
>
>
> Also noticed a bunch of trailing white spaces.
I fixed those in the updated patch I sent.
> I am not opposed to the idea of the patch, I think it is indeed useful
> for post-processing tools.
yeah
- Arnaldo
next prev parent reply other threads:[~2013-03-13 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 2:43 [PATCH] perf, tools: Make perf stat -I ... CSV output flat Andi Kleen
2013-03-12 20:24 ` Arnaldo Carvalho de Melo
2013-03-13 13:19 ` Stephane Eranian
2013-03-13 15:49 ` Arnaldo Carvalho de Melo [this message]
2013-03-13 16:56 ` Andi Kleen
2013-03-14 11:26 ` Stephane Eranian
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=20130313154928.GA15763@infradead.org \
--to=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
/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