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]

Date:	Wed, 8 Jun 2016 18:25:29 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	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, bp@...en8.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86/intel: Use Intel family macros for core
 perf events


* Vince Weaver <vincent.weaver@...ne.edu> wrote:

> eventually you can get them to send /proc/cpuinfo so you can try to find 
> out what processor they really have, and in that case you can get
> the family/model numbers in plain decimal, and you can easily look up
> if things are supported in the various files.

If only it was that simple! /proc/cpuinfo lists the model number in decimal, but 
half of all uses were in hexa, making grepping hard ...

So the real solution would be to print out the engineering model name in 
/proc/cpuinfo as well:

 processor       : 119
 vendor_id       : GenuineIntel
 cpu family      : 6
 model           : 62
 model name      : Intel(R) Xeon(R) CPU E7-4890 v2 @ 2.80GHz
 model string    : IvyBridge_X

... or something like that. The string could even be auto-generated from the list 
in intel-family.h?

Thanks,

	Ingo