linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, x86@kernel.org,
	Dave Hansen <dave.hansen@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tony Luck <tony.luck@intel.com>
Subject: [PATCH -v2 5/5] x86/intel: Add common OPTDIFFs
Date: Tue, 27 Aug 2019 21:48:25 +0200	[thread overview]
Message-ID: <20190827195122.731530141@infradead.org> (raw)
In-Reply-To: 20190827194820.378516765@infradead.org


Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: x86@kernel.org
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Tony Luck <tony.luck@intel.com>
---
 arch/x86/include/asm/intel-family.h |   21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

--- a/arch/x86/include/asm/intel-family.h
+++ b/arch/x86/include/asm/intel-family.h
@@ -5,9 +5,6 @@
 /*
  * "Big Core" Processors (Branded as Core, Xeon, etc...)
  *
- * The "_X" parts are generally the EP and EX Xeons, or the
- * "Extreme" ones, like Broadwell-E, or Atom microserver.
- *
  * While adding a new CPUID for a new microarchitecture, add a new
  * group to keep logically sorted out in chronological order. Within
  * that group keep the CPUID for the variants sorted by model number.
@@ -21,9 +18,19 @@
  * MICROARCH	Is the code name for the micro-architecture for this core.
  *		N.B. Not the platform name.
  * OPTDIFF	If needed, a short string to differentiate by market segment.
- *		Exact strings here will vary over time. _DESKTOP, _MOBILE, and
- *		_X (short for Xeon server) should be used when they are
- *		appropriate.
+ *
+ *		Common OPTDIFFs:
+ *
+ *			- regular client parts
+ *		_L	- regular mobile parts
+ *		_G	- parts with extra graphics on
+ *		_X	- regular server parts
+ *		_D	- micro server parts
+ *
+ *		Historical OPTDIFFs:
+ *
+ *		_EP	- 2 socket server parts
+ *		_EX	- 4+ socket server parts
  *
  * The #define line may optionally include a comment including platform names.
  */
@@ -91,6 +98,8 @@
 
 #define INTEL_FAM6_ATOM_GOLDMONT	0x5C /* Apollo Lake */
 #define INTEL_FAM6_ATOM_GOLDMONT_D	0x5F /* Denverton */
+
+/* Note: the micro-architecture is "Goldmont Plus" */
 #define INTEL_FAM6_ATOM_GOLDMONT_PLUS	0x7A /* Gemini Lake */
 
 #define INTEL_FAM6_ATOM_TREMONT_D	0x86 /* Jacobsville */



  parent reply	other threads:[~2019-08-27 19:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 19:48 [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 1/5] x86/intel: Aggregate big core client naming Peter Zijlstra
2019-08-28 13:03   ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 2/5] x86/intel: Aggregate big core mobile naming Peter Zijlstra
2019-08-28 13:03   ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 3/5] x86/intel: Aggregate big core graphics naming Peter Zijlstra
2019-08-28 13:03   ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` [PATCH -v2 4/5] x86/intel: Aggregate microserver naming Peter Zijlstra
2019-08-28 13:03   ` [tip: x86/cpu] " tip-bot2 for Peter Zijlstra
2019-08-27 19:48 ` Peter Zijlstra [this message]
2019-08-28 13:03   ` [tip: x86/cpu] x86/intel: Add common OPTDIFFs tip-bot2 for Peter Zijlstra
2019-08-27 20:44 ` [PATCH -v2 0/5] Further sanitize INTEL_FAM6 naming Luck, Tony
2019-08-27 21:51   ` Peter Zijlstra
2019-08-28  9:33     ` Peter Zijlstra
2019-08-28 12:59       ` Peter Zijlstra
2019-08-28 15:03         ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190827195122.731530141@infradead.org \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).