linux-kernel - Re: git bisect and perf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 05 Jun 2012 18:05:12 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	David Ahern <dsahern@...il.com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Stephane Eranian <eranian@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: git bisect and perf

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.
--
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/