From: tip-bot for Tony Luck <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: x86@kernel.org, tony.luck@intel.com, mingo@redhat.com,
tglx@linutronix.de, hpa@zytor.com, mingo@kernel.org, bp@suse.de,
dave.hansen@intel.com, linux-kernel@vger.kernel.org,
bp@alien8.de
Subject: [tip:x86/urgent] x86/cpu: Explain Intel model naming convention
Date: Sat, 17 Aug 2019 01:19:13 -0700 [thread overview]
Message-ID: <tip-12ece2d53d3e8f827e972caf497c165f7729c717@git.kernel.org> (raw)
In-Reply-To: <20190815224704.GA10025@agluck-desk2.amr.corp.intel.com>
Commit-ID: 12ece2d53d3e8f827e972caf497c165f7729c717
Gitweb: https://git.kernel.org/tip/12ece2d53d3e8f827e972caf497c165f7729c717
Author: Tony Luck <tony.luck@intel.com>
AuthorDate: Thu, 15 Aug 2019 11:16:24 -0700
Committer: Borislav Petkov <bp@suse.de>
CommitDate: Sat, 17 Aug 2019 10:06:32 +0200
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-672ff915db47@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 <bp@alien8.de>
Signed-off-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: x86-ml <x86@kernel.org>
Link: https://lkml.kernel.org/r/20190815224704.GA10025@agluck-desk2.amr.corp.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.
*/
#define INTEL_FAM6_CORE_YONAH 0x0E
next prev parent reply other threads:[~2019-08-17 8:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 23:40 [PATCH] MAINTAINERS, x86/CPU: Tony Luck will maintain asm/intel-family.h Tony Luck
2019-08-15 7:58 ` Borislav Petkov
2019-08-15 17:21 ` Luck, Tony
2019-08-15 17:54 ` Borislav Petkov
2019-08-15 18:30 ` Luck, Tony
2019-08-15 18:35 ` Borislav Petkov
2019-08-15 20:22 ` Thomas Gleixner
2019-08-15 22:47 ` Luck, Tony
2019-08-16 6:46 ` Borislav Petkov
2019-08-16 16:29 ` Luck, Tony
2019-08-16 16:33 ` David Laight
2019-08-16 19:03 ` Borislav Petkov
2019-08-16 7:01 ` Thomas Gleixner
2019-08-17 8:19 ` tip-bot for Tony Luck [this message]
2019-08-20 15:30 ` Peter Zijlstra
2019-08-20 15:40 ` Peter Zijlstra
2019-08-20 15:49 ` Peter Zijlstra
2019-08-20 15:53 ` Peter Zijlstra
2019-08-21 16:45 ` Luck, Tony
2019-08-20 16:10 ` Peter Zijlstra
2019-08-15 8:01 ` [tip:x86/urgent] " tip-bot for Tony Luck
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=tip-12ece2d53d3e8f827e972caf497c165f7729c717@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--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