From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, len.brown@intel.com,
ak@linux.intel.com, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake
Date: Tue, 7 Aug 2018 19:34:24 +0200 [thread overview]
Message-ID: <20180807173424.GH2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1533662247-17575-1-git-send-email-kan.liang@linux.intel.com>
On Tue, Aug 07, 2018 at 10:17:27AM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> Denverton and Gemini Lake are platform names and should not be used for
> Processor Family stuff. The microarchitecture codename should be used.
>
> DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar
> to SILVERMONT2 being the silvermont server SoCs.
>
> Rename GEMINI_LAKE to GOLDMONT_PLUS.
>
> Suggested-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
Thanks! the alternative to 2 is _X like we have with the big cores to
denote server chips, but this is already a nice improvement.
next prev parent reply other threads:[~2018-08-07 17:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:17 [PATCH] x86/cpu: Rename Denverton and Gemini Lake kan.liang
2018-08-07 17:34 ` Peter Zijlstra [this message]
2018-08-07 17:35 ` Dave Hansen
2018-08-07 17:48 ` Peter Zijlstra
2018-08-07 18:29 ` Dave Hansen
2018-08-07 18:37 ` Andi Kleen
2018-08-07 19:59 ` Peter Zijlstra
2018-08-07 21:10 ` Thomas Gleixner
2018-08-07 22:17 ` Andi Kleen
2018-08-08 5:14 ` Thomas Gleixner
2018-08-08 14:07 ` Arnd Bergmann
2018-09-27 14:25 ` Peter Zijlstra
2018-09-27 14:49 ` Thomas Gleixner
2018-09-27 14:57 ` Peter Zijlstra
2018-09-27 15:00 ` Thomas Gleixner
2018-09-27 14:53 ` Dave Hansen
2018-09-28 16:07 ` Alan Cox
2018-09-28 19:18 ` Peter Zijlstra
2018-08-07 18:35 ` Andi Kleen
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=20180807173424.GH2494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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