On Thu, 15 Aug 2019, Luck, Tony wrote: > >From 093bf8cd02f4c7a3fa256c2cf7302014190e2840 Mon Sep 17 00:00:00 2001 > From: Tony Luck <tony.l...@intel.com> > Date: Thu, 15 Aug 2019 11:16:24 -0700 > Subject: [PATCH] x86/cpu: Explain Intel model naming convention > > Dave Hansen spelled out the rules in an e-mail: > > https://lkml.kernel.org/r/91eefbe4-e32b-d762-be4d-672ff915d...@intel.com > > Copy those right into the <asm/intel-family.h> file to > make it easy for people to find them. > > Suggested-by: Borislav Petkov <b...@alien8.de> > Signed-off-by: Tony Luck <tony.l...@intel.com> > --- > arch/x86/include/asm/intel-family.h | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/arch/x86/include/asm/intel-family.h > b/arch/x86/include/asm/intel-family.h > index 0278aa66ef62..fe7c205233f1 100644 > --- a/arch/x86/include/asm/intel-family.h > +++ b/arch/x86/include/asm/intel-family.h > @@ -11,6 +11,21 @@ > * 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. > + * > + * The defined symbol names have the following form: > + * INTEL_FAM6{OPTFAMILY}_{MICROARCH}{OPTDIFF} > + * where: > + * OPTFAMILY Describes the family of CPUs that this belongs to. Default > + * is assumed to be "_CORE" (and should be omitted). Other values > + * currently in use are _ATOM and _XEON_PHI > + * 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. > + * > + * The #define line may optionally include a comment including platform > names. > */
Acked-by: Thomas Gleixner <t...@linutronix.de>
