[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160608141608.GB19090@pd.tnic>
Date: Wed, 8 Jun 2016 16:16:08 +0200
From: Borislav Petkov <bp@...en8.de>
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,
mingo@...nel.org, 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 10:09:28AM -0400, Vince Weaver wrote:
> and don't get me started about trying to somehow match a model number to a
> code name using the AMD or intel documentation, without resorting to
> wikipedia or random tech sites. I'm looking at you AMD fam15h model 60h.
That's easy - Carrizo :-P
But seriously, should we do some mapping of those somewhere and then
have people look at them and point at the exact f/m/s they mean?
This issue has come up in the past too; it is one of the reasons I added
f/m/s to the boot string:
[ 0.303209] AMD-Vi: Command-line override present for HPET id 0 - ignoring
[ 0.389353] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.542398] smpboot: CPU0: AMD FX(tm)-8350 Eight-Core Processor (family: 0x15, model: 0x2, stepping: 0x0)
^^^^^^^^^^^
[ 0.552219] Performance Events: Fam15h core perfctr, AMD PMU driver.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Powered by blists - more mailing lists