linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, tony.luck@intel.com, "Liang,
	Kan" <kan.liang@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/cpu: Resort and comment Intel models
Date: Mon, 15 Mar 2021 17:23:38 +0100	[thread overview]
Message-ID: <20210315162338.GF20497@zn.tnic> (raw)
In-Reply-To: <YE+HhS8i0gshHD3W@hirez.programming.kicks-ass.net>

On Mon, Mar 15, 2021 at 05:12:53PM +0100, Peter Zijlstra wrote:
> 
> The INTEL_FAM6 list has become a mess again. Try and bring some sanity
> back into it.
> 
> Where previously we had one microarch per year and a number of SKUs
> within that, this no longer seems to be the case. We now get dfferent

"different"

> uarch names that share a 'core' design.

Soon it'll be all an unrecognizable mess with IP blocks tetris. :-)

> Add the core name starting at skylake and reorder to keep the cores in
> chronological order. Furthermore, Intel marketed the names {Amber,
> Coffee, Whiskey} Lake, but those are in fact steppings of Kaby Lake, add
> comments for them.
> 
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> Note: we don't seem to have CANNONLAKE perf support.
> 
>  arch/x86/include/asm/intel-family.h | 50 +++++++++++++++++++++----------------
>  1 file changed, 28 insertions(+), 22 deletions(-)

Anything that helps clear more of this names confusion:

Acked-by: Borislav Petkov <bp@suse.de>

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-03-15 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 16:12 Peter Zijlstra
2021-03-15 16:23 ` Borislav Petkov [this message]
2021-04-08 12:30 ` [tip: x86/core] " tip-bot2 for Peter Zijlstra

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=20210315162338.GF20497@zn.tnic \
    --to=bp@alien8.de \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH] x86/cpu: Resort and comment Intel models' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).