From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, paulus@samba.org, davem@davemloft.net,
fweisbec@gmail.com, perfmon2-devel@lists.sf.net,
eranian@gmail.com, robert.richter@amd.com
Subject: Re: [PATCH] perf: add csv-style output to perf stat (v2)
Date: Wed, 1 Dec 2010 16:10:01 -0200 [thread overview]
Message-ID: <20101201181001.GA26071@ghostprotocols.net> (raw)
In-Reply-To: <4cf68aa7.0fedd80a.5294.1203@mx.google.com>
Em Wed, Dec 01, 2010 at 06:49:05PM +0200, Stephane Eranian escreveu:
> This patch adds an option (-x/--field-separator) to print counts using
> a CSV-style output. The user can pass a custom separator. This makes it
> very easy to import counts directly into your favorite spreadsheet without
> having to write scripts.
>
> Example:
> $ perf stat --field-separator=, -a -- sleep 1
> 4009.961740,task-clock-msecs
> 13,context-switches
> 2,CPU-migrations
> 189,page-faults
> 9596385684,cycles
> 3493659441,instructions
> 872897069,branches
> 41562,branch-misses
> 22424,cache-references
> 1289,cache-misses
[root@mica ~]# perf stat -x, -a -A -- sleep 1
-B option not supported with -x
usage: perf stat [<options>] [<command>]
-e, --event <event> event selector. use 'perf list' to list
available events
-i, --no-inherit child tasks do not inherit counters
-p, --pid <n> stat events on existing process id
Guess we'll have to disable big_num automatically when -x is specified,
but at the same time notice if the user _explicitely_ asked for -B.
I'll fix this now.
- Arnaldo
next prev parent reply other threads:[~2010-12-01 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:49 Stephane Eranian
2010-12-01 18:10 ` Arnaldo Carvalho de Melo [this message]
2010-12-01 18:54 ` Arnaldo Carvalho de Melo
2010-12-03 16:46 ` Stephane Eranian
2010-12-03 18:29 ` Arnaldo Carvalho de Melo
2010-12-02 11:48 ` [tip:perf/core] perf stat: Add csv-style output tip-bot for 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=20101201181001.GA26071@ghostprotocols.net \
--to=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
/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
Powered by JetHome