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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 8 Jun 2016 12:51:45 -0700
From:	Stephane Eranian <eranian@...gle.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Vince Weaver <vincent.weaver@...ne.edu>,
	Thomas Gleixner <tglx@...utronix.de>, brgerst@...il.com,
	Dave Hansen <dave@...1.net>,
	"Liang, Kan" <kan.liang@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
	Jiri Olsa <jolsa@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>, dvlasenk@...hat.com,
	"H. Peter Anvin" <hpa@...or.com>, dave.hansen@...ux.intel.com,
	Andy Lutomirski <luto@...capital.net>,
	"linux-tip-commits@...r.kernel.org" 
	<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 8, 2016 at 9:34 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Wed, Jun 08, 2016 at 06:25:29PM +0200, Ingo Molnar wrote:
>>  model string    : IvyBridge_X
>>
>> ... or something like that. The string could even be auto-generated from the list
>> in intel-family.h?
>
> Yap, that sounds cool too. And then we should issue that too during boot:
>
I like that approach too. It avoids going online to check what
micro-architecture the number maps too.
Yet, I wonder how portable that is.

> [    0.542398] smpboot: CPU0: AMD FX(tm)-8350 Eight-Core Processor (family: 0x15, model: 0x2, stepping: 0x0; Piledriver)
>
> so that we don't need to ask for dmesg *and* /proc/cpuinfo.
>
> Hohumm, this should be very useful.
>
> --
> Regards/Gruss,
>     Boris.
>
> ECO tip #101: Trim your mails when you reply.