From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>, x86@kernel.org
Cc: bp@suse.de, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
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 09:19:23 -0400 [thread overview]
Message-ID: <9ea08a94-a3e0-0e89-401b-a240e1bce7fa@linux.intel.com> (raw)
In-Reply-To: <20190808101045.19239-1-rajneesh.bhardwaj@linux.intel.com>
On 8/8/2019 6:10 AM, Rajneesh Bhardwaj wrote:
> Elkhart Lake is Atom based SoC that uses model number 0x96. CPUID details
> will be documented in a future version of Intel Software Development
> Manual.
>
> Cc: bp@suse.de
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Kan Liang <kan.liang@linux.intel.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: x86-ml <x86@kernel.org>
> Cc: Linux PM <linux-pm@vger.kernel.org>
> Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>
> ---
> arch/x86/include/asm/intel-family.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/include/asm/intel-family.h b/arch/x86/include/asm/intel-family.h
> index 0278aa66ef62..06e94ae65f28 100644
> --- a/arch/x86/include/asm/intel-family.h
> +++ b/arch/x86/include/asm/intel-family.h
> @@ -79,6 +79,7 @@
> #define INTEL_FAM6_ATOM_GOLDMONT_PLUS 0x7A /* Gemini Lake */
>
> #define INTEL_FAM6_ATOM_TREMONT_X 0x86 /* Jacobsville */
> +#define INTEL_FAM6_ATOM_ELKHART_LAKE 0x96 /*Elkhart Lake */
Usually, we should use the code name of microarchitecture for the name
of CPUID.
Thanks,
Kan
>
> /* Xeon Phi */
>
>
next prev parent reply other threads:[~2019-08-08 13:19 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 [this message]
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
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=9ea08a94-a3e0-0e89-401b-a240e1bce7fa@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.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 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.