From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
mingo@elte.hu, "David Ahern" <dsahern@gmail.com>,
"Robert Richter" <robert.richter@amd.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Jiri Olsa" <jolsa@redhat.com>
Subject: Re: [BUG] perf stat: useless output for raw events with new event parser
Date: Mon, 23 Apr 2012 12:48:52 +0200 [thread overview]
Message-ID: <1335178132.28150.117.camel@twins> (raw)
In-Reply-To: <CABPqkBQJU2vYLbr-=qjkpG=sB8n-8aXJ3QkWcASzy5h4rtFAig@mail.gmail.com>
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.
Jiri?
next prev parent reply other threads:[~2012-04-23 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 10:45 [BUG] perf stat: useless output for raw events with new event parser Stephane Eranian
2012-04-23 10:48 ` Peter Zijlstra [this message]
2012-04-23 10:55 ` Jiri Olsa
2012-04-23 10:56 ` Robert Richter
2012-04-23 11:17 ` Stephane Eranian
2012-04-26 10:27 ` Peter Zijlstra
2012-04-26 12:53 ` Stephane Eranian
2012-04-26 14:03 ` Peter Zijlstra
2012-04-26 13:12 ` Robert Richter
2012-04-26 14:24 ` Peter Zijlstra
2012-04-26 14:45 ` Robert Richter
2012-04-26 15:39 ` Peter Zijlstra
2012-04-26 17:36 ` Robert Richter
2012-05-07 12:42 ` Peter Zijlstra
2012-05-07 16:58 ` Robert Richter
2012-04-23 10:57 ` Jiri Olsa
2012-05-02 11:14 ` 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=1335178132.28150.117.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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