[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120423105525.GC1720@m.brq.redhat.com>
Date: Mon, 23 Apr 2012 12:55:25 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Stephane Eranian <eranian@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>, mingo@...e.hu,
David Ahern <dsahern@...il.com>,
Robert Richter <robert.richter@....com>,
Frédéric Weisbecker <fweisbec@...il.com>
Subject: Re: [BUG] perf stat: useless output for raw events with new event
parser
On Mon, Apr 23, 2012 at 12:48:52PM +0200, Peter Zijlstra wrote:
> On Mon, 2012-04-23 at 12:45 +0200, Stephane Eranian wrote:
> > Hi,
> >
> > With the new event parser, one can express raw events field by field:
> >
> > $ perf stat -e cpu/event=0x3c,umask=0x0/,cpu/event=0xc5,umask=0x0/ noploop 1
> >
> > The problem with this is that the output of perf stat becomes useless:
> >
> > $ perf stat -e cpu/event=0x3c,umask=0x0/,cpu/event=0xc5,umask=0x0/ noploop 1
> > noploop for 1 seconds
> >
> > Performance counter stats for 'noploop 1':
> >
> > 2395038678 pmu
> > 10787 pmu
> > ^^^^^^
> > 1.000802603 seconds time elapsed
>
> Yeah, I already complained about that.. Jolsa proposed adding a name=
> parameter so you could explicitly name your events. I think I've seen a
> patch adding that, but can't atm seem to locate it.
it's waiting in here:
https://lkml.org/lkml/2012/4/15/74
I already talked to Arnaldo and I need to resend this serie,
due to another changes that are yet about to get into tip tree..
Once it's in, I'll resend ;)
jirka
>
> Jiri?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists