From: Thomas Gleixner <tglx@linutronix.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS, x86/CPU: Tony Luck will maintain asm/intel-family.h
Date: Thu, 15 Aug 2019 22:22:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908152217070.1908@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190815183055.GA6847@agluck-desk2.amr.corp.intel.com>
On Thu, 15 Aug 2019, Luck, Tony wrote:
> On Thu, Aug 15, 2019 at 07:54:55PM +0200, Borislav Petkov wrote:
> @@ -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.
> + *
> + * HOWTO Build an INTEL_FAM6_ definition:
> + *
> + * 1. Start with INTEL_FAM6_
> + * 2. If not Core-family, add a note about it, like "ATOM". There are only
> + * two options for this (Xeon Phi and Atom). It is exceedingly unlikely
> + * that you are adding a cpu which needs a new option here.
> + * 3. Add the processor microarchitecture, not the platform name
> + * 4. Add a short differentiator if necessary. Add an _X to differentiate
> + * Server from Client.
We have the following existing _SHORT variants:
_G
_EP
_EX
_CORE
_ULT
_GT3E
_XEON_D
_MOBILE
_DESKTOP
_NNPI
_MID
_TABLET
_PLUS
So we should document the list of valid and usable ones and either fixup
broken ones or document that they are historic ballast and not to be used
for new ones. Otherwise you end up with the same discussions again.
Thanks,
tglx
next prev parent reply other threads:[~2019-08-15 20:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 23:40 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 [this message]
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:x86/urgent] x86/cpu: Explain Intel model naming convention tip-bot for Tony Luck
2019-08-20 15:30 ` [PATCH] MAINTAINERS, x86/CPU: Tony Luck will maintain asm/intel-family.h 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=alpine.DEB.2.21.1908152217070.1908@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome