mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	"Yan, Zheng" <zheng.z.yan@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Maria Dimakopoulou <maria.n.dimakopoulou@gmail.com>
Subject: Re: [PATCH v4 2/4] perf stat: add event unit and scale support
Date: Tue, 5 Nov 2013 15:00:30 +0100	[thread overview]
Message-ID: <20131105140030.GA30283@krava.brq.redhat.com> (raw)
In-Reply-To: <CABPqkBQ1Kv9MMBhRdNoBA4k=n=cGVQtuUn810P7-PSu_SRwLug@mail.gmail.com>

On Tue, Nov 05, 2013 at 02:34:45PM +0100, Stephane Eranian wrote:
> Hi,
> 
> One thing I realized while testing is that we cannot simply add the
> unit printout like that.
> This may break all the scripts people may have written to parse the
> output of perf stat.

isn't it what the -x output is meant for?

  perf stat -x, ...

  1.738605,task-clock
  367,context-switches
  0,cpu-migrations
  272,page-faults
  6722006,cycles
  2592661,stalled-cycles-frontend
  1935855,stalled-cycles-backend
  4324013,instructions
  823229,branches
  11192,branch-misses

> I think we need to make the display of the unit optional. If I do:
>    $ perf stat -e cycles ls
> 
> The output should remain as it was before and not show:
> $ perf stat -e cycles ls
>       22782847475 ? cycles

maybe we should display just space ' ' instead
of the '?' ...seems confusing

> 
> So I think we need a --show-unit option. It would be off by default.
> Of course doing this causes a mess with the current code because
> of all the various printf() in builtin-stat.c but I think it is better for
> the end user.
> 
> Any opinion?

I haven't checked by I think we changed the default perf stat
output in the past without any fuzz

maybe just keep the -x output or add the unit
to the end of the line

jirka

  reply	other threads:[~2013-11-05 14:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 14:59 [PATCH v4 0/4] perf/x86: add Intel RAPL PMU support Stephane Eranian
2013-10-31 14:59 ` [PATCH v4 1/4] perf: add active_entry list head to struct perf_event Stephane Eranian
2013-10-31 14:59 ` [PATCH v4 2/4] perf stat: add event unit and scale support Stephane Eranian
2013-11-01 10:57   ` Jiri Olsa
2013-11-04 14:47     ` Stephane Eranian
2013-11-04 14:51       ` Jiri Olsa
2013-11-05 13:34         ` Stephane Eranian
2013-11-05 14:00           ` Jiri Olsa [this message]
2013-11-05 14:04             ` Stephane Eranian
2013-11-05 14:16           ` Andi Kleen
2013-11-05 14:17             ` Stephane Eranian
2013-11-05 15:03               ` Stephane Eranian
2013-10-31 14:59 ` [PATCH v4 3/4] perf/x86: add Intel RAPL PMU support Stephane Eranian
2013-10-31 15:14   ` Peter Zijlstra
2013-10-31 14:59 ` [PATCH v4 4/4] perf,x86: add RAPL hrtimer support 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=20131105140030.GA30283@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maria.n.dimakopoulou@gmail.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=zheng.z.yan@intel.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

all inboxes | Powered by JetHome®