From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757616AbcFHQZh (ORCPT <rfc822;w@1wt.eu>);
	Wed, 8 Jun 2016 12:25:37 -0400
Received: from mail-wm0-f53.google.com ([74.125.82.53]:36109 "EHLO
	mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757583AbcFHQZe (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 8 Jun 2016 12:25:34 -0400
Date: Wed, 8 Jun 2016 18:25:29 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: tglx@linutronix.de, brgerst@gmail.com, dave@sr71.net, kan.liang@intel.com,
        torvalds@linux-foundation.org, acme@redhat.com,
        alexander.shishkin@linux.intel.com, jolsa@redhat.com,
        linux-kernel@vger.kernel.org, eranian@google.com, peterz@infradead.org,
        dvlasenk@redhat.com, hpa@zytor.com, dave.hansen@linux.intel.com,
        luto@amacapital.net, bp@alien8.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf/x86/intel: Use Intel family macros for core
 perf events
Message-ID: <20160608162529.GA25133@gmail.com>
References: <20160603001929.C5F1C079@viggo.jf.intel.com>
 <tip-ef5f9f47d4ec4cf42bac48c7c4dafacc1b9f0630@git.kernel.org>
 <alpine.DEB.2.20.1606081001110.5993@macbook-air>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1606081001110.5993@macbook-air>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Vince Weaver <vincent.weaver@maine.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