From: David Ahern <dsahern@gmail.com>
To: yipeng <yipeng@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf stat: Doubt about stall cycle support
Date: Wed, 21 Mar 2012 10:24:28 -0600 [thread overview]
Message-ID: <4F6A00BC.8070705@gmail.com> (raw)
In-Reply-To: <CAB_n8zK5b0jWA=retCX12DGmrb19gMd2UxJGWkn6HD9nFrdiAQ@mail.gmail.com>
On 3/21/12 9:32 AM, yipeng wrote:
>
> What does perf --version show?
>
> Should be fixed by 2cee77c4505fc581f41b44e18ffc09__53b67a414c.
>
> David
>
>
> I'm not sure what version that hash is. I'm using perf version
> 3.0.22. Is my version that too old?
That's a commit id for perf-stat to discriminate unsupported events from
not counted events.
It was committed around 3.0 timeframe. Try compiling a newer version of
perf and see if it addresses your concern.
David
next prev parent reply other threads:[~2012-03-21 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 4:42 perf stat: Doubt about stall cycle support Yipeng Huang
2012-03-21 14:46 ` David Ahern
[not found] ` <CAB_n8zK5b0jWA=retCX12DGmrb19gMd2UxJGWkn6HD9nFrdiAQ@mail.gmail.com>
2012-03-21 16:24 ` David Ahern [this message]
2012-03-22 0:43 ` Yipeng Huang
2012-03-22 1:17 ` Vince Weaver
2012-03-24 1:55 ` yipeng
2012-03-22 2:30 ` David Ahern
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=4F6A00BC.8070705@gmail.com \
--to=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=yipeng@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.