Linux Power Management development
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@linux.intel.com>
Cc: "Liang, Kan" <kan.liang@linux.intel.com>,
	x86@kernel.org, bp@suse.de, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Qiuxu Zhuo <qiuxu.zhuo@intel.com>, Len Brown <lenb@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] x86/cpu: Add Elkhart Lake to Intel family
Date: Thu, 8 Aug 2019 19:37:50 +0200	[thread overview]
Message-ID: <20190808173750.GN2369@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <76d459fd-5d23-6d1a-1d2d-30205ec5a518@linux.intel.com>

On Thu, Aug 08, 2019 at 09:20:03PM +0530, Bhardwaj, Rajneesh wrote:
> 
> On 08-Aug-19 9:01 PM, Peter Zijlstra wrote:
> > On Thu, Aug 08, 2019 at 05:23:26PM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 08, 2019 at 08:40:49PM +0530, Bhardwaj, Rajneesh wrote:
> > > > On 08-Aug-19 7:44 PM, Peter Zijlstra wrote:
> > > > > On Thu, Aug 08, 2019 at 09:19:23AM -0400, Liang, Kan wrote:
> > > > > > Usually, we should use the code name of microarchitecture for the name of
> > > > > > CPUID.
> > > > > Oh yes, very much. A quick google seems to suggest these are in fact
> > > > > Tremont cores. So then the naming should be:
> > > > > 
> > > > >     INTEL_FAM6_ATOM_TREMONT_xxx
> > > > Sure, I feel INTEL_FAM6_ATOM_TREMONT_ELKHART_LAKE may be too long so is
> > > > INTEL_FAM6_ATOM_TREMONT_PLUS a better name?
> > > Neither. WikiChip says it is the successor to Denverton, which is a
> > > server chip. If this is true then:
> > > 
> > > #define INTEL_FAM6_ATOM_TREMONT_X	0x.. /* Elkhart Lake */
> > > 
> > > is what it should be.
> > Of course we already have a TREMONT_X :-/ WikiChip is also confusing me
> > further by stating that Jacobsville is the platform that carries the
> > Elkhart Lake core, so they should be the bloody same chip.
> > 
> > But here we are, with two different model numbers.
> > 
> > Can someone please spell out in dummy language wth these chips are?
> > 
> > Are they both server chips?
> 
> 
> Elkhart Lake is Intel Atom based CPU product targeting primarily PC Client,
> IOT and industrial segments.  Jacobsville is Atom (Tremont) based
> Microserver.

Can we classify 'PC Client, IoT and Industrial' as MID ? Or rather, can
we say this Elkhart Lake is the successor to Moorefield? If not, what is
it successor to?

> Internally, preferred acronym for Elkhart Lake is EHL so does
> INTEL_FAM6_ATOM_TREMONT_EHL look ok?

No; that would be wildly inconsistent with everything else.

Also, I would suggest correcting wikichip and creating a tremont
(microarchitecture) wikipedia page.  There is a distinct lack of public
information on this.

      parent reply	other threads:[~2019-08-08 17:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 10:10 [PATCH] x86/cpu: Add Elkhart Lake to Intel family Rajneesh Bhardwaj
2019-08-08 10:42 ` Peter Zijlstra
2019-08-08 12:28   ` Bhardwaj, Rajneesh
2019-08-08 12:47     ` Peter Zijlstra
2019-08-08 13:19 ` Liang, Kan
2019-08-08 13:56   ` Dave Hansen
2019-08-08 15:14     ` Bhardwaj, Rajneesh
2019-08-08 15:24       ` Borislav Petkov
2019-08-08 14:14   ` Peter Zijlstra
2019-08-08 15:10     ` Bhardwaj, Rajneesh
2019-08-08 15:16       ` Borislav Petkov
2019-08-08 15:23       ` Peter Zijlstra
2019-08-08 15:28         ` Borislav Petkov
2019-08-08 15:31         ` Peter Zijlstra
2019-08-08 15:50           ` Bhardwaj, Rajneesh
2019-08-08 16:27             ` Liang, Kan
2019-08-08 16:30               ` Dave Hansen
2019-08-08 16:38                 ` Borislav Petkov
2019-08-08 16:54                   ` Dave Hansen
2019-08-08 17:30                     ` Borislav Petkov
2019-08-08 19:24                       ` Dave Hansen
2019-08-08 19:30                         ` Borislav Petkov
2019-08-08 17:54                     ` Peter Zijlstra
2019-08-08 17:38               ` Peter Zijlstra
2019-08-08 17:37             ` Peter Zijlstra [this message]

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=20190808173750.GN2369@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kan.liang@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=rajneesh.bhardwaj@linux.intel.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