linux-kernel - Re: [PATCH] oprofile: Add Support for Intel CPU Family 6 / Model 29

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: <20100922072633.GV13563@erda.amd.com>
Date:	Wed, 22 Sep 2010 09:26:33 +0200
From:	Robert Richter <robert.richter@....com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Arnd Bergmann <arnd@...db.de>, Jiri Olsa <jolsa@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"oprofile-list@...ts.sourceforge.net" 
	<oprofile-list@...ts.sourceforge.net>,
	"tdm.rhbz@...il.com" <tdm.rhbz@...il.com>
Subject: Re: [PATCH] oprofile: Add Support for Intel CPU Family 6 / Model 29

On 21.09.10 10:38:04, Andi Kleen wrote:
> > On 21.09.10 07:21:05, Arnd Bergmann wrote:
> >> Just curious about the other missing IDs: this now supports all Core
> >> microarchitecture CPUs, but only some Nehalem/Westmere ones.
> >>
> >> There is support for 0x1a (Bloomfield/Gainestown) and 0x2e (Beckton),
> >> but
> >> not for the much more common 0x1e (Lynnfield/Clarksfield/Jasper Forest),
> >> 0x25 (Clarkdale/Arrandale) and 0x26 (Gulftown/Westmere-EP).

I also found reports for 0x2c (Gulftown/Westmere-EP?):

vendor_id       : GenuineIntel
cpu family      : 6
model           : 44
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz

-Robert

> >>
> >> Shouldn't those be added as well?
> 
> Westmere I still hold off because the oprofile user land
> doesn't have the correct event list yet.
> 
> BTW I was thinking in this case to only add the model
> numbers to the user code and just let it handle arch_perfmon
> from the kernel.
> 
> This should work currently fine and avoid the problem
> that you need to update user land and kernel in parallel
> for a new cpu type.
> 
> >>
> >> When you're there, it probably also wouldn't hurt to fill in the blanks
> >> of some of the older CPUs like Tolopai (0x15) and newer Atoms (0x1c).
> >
> > Yes, would be nice to have also an update for the remaining
> > unsupported models. Andi?
> 
> Yes would make sense. I'll ask around if there is a consolidated
> list somewhere that could be used as a base.
> 
> -Andi
> 
> 

-- 
Advanced Micro Devices, Inc.
Operating System Research Center

--
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/