From: Andi Kleen <ak@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
kan.liang@linux.intel.com, mingo@redhat.com, len.brown@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 15:17:25 -0700 [thread overview]
Message-ID: <20180807221725.GU4238@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1808072257080.1672@nanos.tec.linutronix.de>
> Which simply does not work. Look at Goldmont Fam 6 Model 5C. The SoCs
> with that Fam/Model combination are:
>
> - Apollo Lake
> - Broxton (has two platforms: Morganfield and Willowtrail)
Right pick one. The others are the same for software purposes
and can be handled in the same way.
>
> It's even worse with Silvermont.
>
> So no, the interesting information is the UARCH and the variant of that,
With Uarch you mean the core uarch? That doesn't really work for
something like Silvermont or Goldmont.
> e.g. UARCH_CLIENT, UARCH_SERVER, UARCH_WHATEVER. All the magic Code Names
Right your scheme totally doesn't work on Silvermont because there
are multiple client variants.
> and their platform variants are not interesting at all for the Fam/Model
> information.
You're right platform is misleading. I think the right level
are SOCs, because that matches the how the model numbers are allocated.
On Big Core *Lakes are all unique SOCs.
-Andi
next prev parent reply other threads:[~2018-08-07 22:17 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
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 [this message]
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=20180807221725.GU4238@tassilo.jf.intel.com \
--to=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=peterz@infradead.org \
--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