From: Peter Zijlstra <peterz@infradead.org>
To: David Ahern <dsahern@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: git bisect and perf
Date: Tue, 05 Jun 2012 18:05:12 +0200 [thread overview]
Message-ID: <1338912312.2749.6.camel@twins> (raw)
In-Reply-To: <1338912052.2749.2.camel@twins>
On Tue, 2012-06-05 at 18:00 +0200, Peter Zijlstra wrote:
> On Tue, 2012-06-05 at 09:29 -0600, David Ahern wrote:
> > I am trying find out when (ie. which commit) the pebs feature
> > actually
> > started working on a westmere system
>
> What do you mean with working? The whole cycles:pp thing is magic and
> unrelated to 'regular' PEBS stuff. .35 would indeed be the version we
> introduced PEBS support and it should actually work.
>
> But if you're looking for the cycles:pp stuff (commit 7639dae0ca1)
> that's .38-rc1-ish.
So on kernels pre that commit you could still do:
perf record -e r108000c0:pp
and get the same effect. Its just that after that commit r3c:pp will be
magically translated to the above.
And just to be complete (as Stephane always needs to point out) event 3c
and 108000c0 aren't fully identical, they differ in that one counts
while idle and the other doesn't (but I forgot which way around).
Luckily not a lot of people care about profiling idle time.
next prev parent reply other threads:[~2012-06-05 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 15:29 git bisect and perf David Ahern
2012-06-05 15:51 ` Roland Dreier
2012-06-05 16:56 ` David Ahern
2012-06-05 16:00 ` Peter Zijlstra
2012-06-05 16:05 ` Peter Zijlstra [this message]
2012-06-05 17:12 ` David Ahern
2012-06-05 17:35 ` Peter Zijlstra
2012-06-05 23:48 ` David Ahern
2012-06-06 11:46 ` Stephane Eranian
2012-06-05 19:04 ` Stephane Eranian
2012-06-05 19:08 ` 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=1338912312.2749.6.camel@twins \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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