linux-kernel - Re: [PATCH 3/3] perf tool: Add non arch events for SandyBridge microarchitecture

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:	Fri, 21 Dec 2012 19:43:24 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Vince Weaver <vince@...ter.net>
Cc:	Jiri Olsa <jolsa@...hat.com>, Andi Kleen <andi@...stfloor.org>,
	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 3/3] perf tool: Add non arch events for SandyBridge microarchitecture

> I hate to sound like a broken record here, but, again, what's the 
> rationalization for not using libpfm4 here?

Personally I always hated the libpfm4 syntax. It's even worse than
oprofile.

> 
> Is it simply NIH or is there some sort of technical reason?  It seems a 
> lot of wasted effort to create all these tables one chip at a time when 
> libpfm4 already has well-tested and debugged event tables for most CPUs 
> with perf_event support.

I'm probably biased, but it's usually best to use the format the CPU
vendor releases the original event tables in. That gives you
the fastest access with the minimum amount of hazzle.

That would need a parser for each vendor, but there aren't really all
that many.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/