From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@linux.intel.com>,
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: Thu, 27 Sep 2018 16:57:45 +0200 [thread overview]
Message-ID: <20180927145745.GD3439@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1809271648210.8118@nanos.tec.linutronix.de>
On Thu, Sep 27, 2018 at 04:49:18PM +0200, Thomas Gleixner wrote:
> > Subject: x86/cpu: Sanitize FAM6_ATOM naming
> > From: Peter Zijlstra <peterz@infradead.org>
> > Date: Tue, 7 Aug 2018 10:17:27 -0700
> >
> > Going primarily by:
> >
> > https://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors#Silvermont_microarchitecture
> >
> > with additional information gleaned from other related pages; notably:
> >
> > - Bonnell shrink was called Saltwell
> > - Moorefield is the Merriefield refresh which makes it Airmont
> >
> > The general naming scheme is: FAM6_ATOM_UARCH_SOCTYPE
> >
> > Cc: x86@kernel.org
> > Cc: mingo@redhat.com
> > Cc: ak@linux.intel.com
> > Cc: tglx@linutronix.de
> > Cc: dave.hansen@linux.intel.com
> > Cc: len.brown@intel.com
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> Which way do we route that?
I have it stuck in with some perf patches, does that work?
next prev parent reply other threads:[~2018-09-27 14:58 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
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 [this message]
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=20180927145745.GD3439@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.