From: Tony Luck <tony.luck@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Tony Luck <tony.luck@intel.com>,
Gayatri Kammela <gayatri.kammela@intel.com>,
Rahul Tanwar <rahul.tanwar@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] New Intel CPU model numbers
Date: Thu, 5 Sep 2019 12:30:16 -0700 [thread overview]
Message-ID: <20190905193020.14707-1-tony.luck@intel.com> (raw)
I'm going to be more aggressive about pushing new CPU model
numbers into <asm/intel-family.h>. Basically as soon as Intel
talks publicly about some new model and I have the model
number, then I'll post the update.
Changes to the rest of the kernel will follow at the
pace of the various groups that have model specific
code ready to be made public.
This series has just the model numbers for Tiger Lake and
Elkhart Lake. The new Airmont variant also comes with a
patch of other spots in the kernel that need updates.
Gayatri Kammela (2):
x86/cpu: Add Tiger Lake to Intel family
x86/cpu: Add Elkhart Lake to Intel family
Rahul Tanwar (2):
x86/cpu: Add new Airmont variant to Intel family
x86/cpu: Update init data for new Airmont CPU model
arch/x86/include/asm/intel-family.h | 5 +++++
arch/x86/kernel/cpu/common.c | 1 +
arch/x86/kernel/cpu/intel.c | 1 +
arch/x86/kernel/tsc_msr.c | 5 +++++
4 files changed, 12 insertions(+)
--
2.20.1
next reply other threads:[~2019-09-05 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 19:30 Tony Luck [this message]
2019-09-05 19:30 ` [PATCH 1/4] x86/cpu: Add Tiger Lake to Intel family Tony Luck
2019-09-05 19:30 ` [PATCH 2/4] x86/cpu: Add Elkhart " Tony Luck
2019-09-05 19:30 ` [PATCH 3/4] x86/cpu: Add new Airmont variant " Tony Luck
2019-09-05 19:30 ` [PATCH 4/4] x86/cpu: Update init data for new Airmont CPU model Tony Luck
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=20190905193020.14707-1-tony.luck@intel.com \
--to=tony.luck@intel.com \
--cc=gayatri.kammela@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rahul.tanwar@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).