linux-kernel - Re: [tip:perf/core] perf/x86/intel: Use Intel family macros for core perf events

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]

Message-ID: <20160608204801.GC28646@pd.tnic>
Date:	Wed, 8 Jun 2016 22:48:01 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	Ingo Molnar <mingo@...nel.org>, tglx@...utronix.de,
	brgerst@...il.com, dave@...1.net, kan.liang@...el.com,
	torvalds@...ux-foundation.org, acme@...hat.com,
	alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
	linux-kernel@...r.kernel.org, eranian@...gle.com,
	peterz@...radead.org, dvlasenk@...hat.com, hpa@...or.com,
	dave.hansen@...ux.intel.com, luto@...capital.net,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86/intel: Use Intel family macros for core
 perf events

On Wed, Jun 08, 2016 at 04:15:25PM -0400, Vince Weaver wrote:
> It's also unclear what internal names matter.  For example is AMD 15h/60h
> "Carrizo" or "Excavator" or both?

Excavator is the core and Carrizo is the APU. I think of it as the
client part.

But this is exactly the problem: what name do we take? Also, sometimes
the core name is important (ISA supported) and sometimes the platform.
It depends on the feature.

Maybe a text file with more free formulations would be better.

...

> (why we need two different interfaces for RAPL is another thing, not
> to mention the fact that powercap you can read the values as a normal
> user but with perf you need to be root to read the exact same thing).

Sounds like it needs some cleaning ...

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.