From: Borislav Petkov <bp@alien8.de>
To: Jia Zhang <zhang.jia@linux.alibaba.com>
Cc: tony.luck@intel.com, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/intel: introduce platform_id
Date: Mon, 15 Jan 2018 11:07:40 +0100 [thread overview]
Message-ID: <20180115100740.emrdb6u4b75ixkbj@pd.tnic> (raw)
In-Reply-To: <1515995003-113069-2-git-send-email-zhang.jia@linux.alibaba.com>
On Mon, Jan 15, 2018 at 01:43:22PM +0800, Jia Zhang wrote:
> Platform ID retrieved from MSR_IA32_PLATFORM_ID may be used as
> a filtration condition in some cases.
>
> Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>
> ---
> arch/x86/include/asm/processor.h | 1 +
> arch/x86/kernel/cpu/intel.c | 7 +++++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
> index d3a67fb..c0b4d47 100644
> --- a/arch/x86/include/asm/processor.h
> +++ b/arch/x86/include/asm/processor.h
> @@ -133,6 +133,7 @@ struct cpuinfo_x86 {
> u16 cpu_index;
> u32 microcode;
> unsigned initialized : 1;
> + u8 platform_id;
Platform ID in cpuinfo?
Nope, I don't think so.
> } __randomize_layout;
>
> struct cpuid_regs {
> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> index b1af220..cee0554 100644
> --- a/arch/x86/kernel/cpu/intel.c
> +++ b/arch/x86/kernel/cpu/intel.c
> @@ -229,6 +229,13 @@ static void early_init_intel(struct cpuinfo_x86 *c)
> }
>
> check_mpx_erratum(c);
> +
> + if ((c->x86 > 6) || (c->x86_model >= 5)) {
> + u32 val[2];
> +
> + rdmsr(MSR_IA32_PLATFORM_ID, val[0], val[1]);
> + c->platform_id = 1 << ((val[1] >> 18) & 7);
> + }
collect_cpu_info() in arch/x86/kernel/cpu/microcode/intel.c already does
that so you already have that info without duplicating it.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-01-15 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 5:43 [PATCH 0/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check Jia Zhang
2018-01-15 5:43 ` [PATCH 1/2] x86/intel: introduce platform_id Jia Zhang
2018-01-15 10:07 ` Borislav Petkov [this message]
2018-01-15 5:43 ` [PATCH 2/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check Jia Zhang
2018-01-15 10:10 ` Borislav Petkov
2018-01-15 13:06 ` Jia Zhang
2018-01-15 14:19 ` Borislav Petkov
2018-01-15 11:48 ` Henrique de Moraes Holschuh
2018-01-15 13:07 ` Jia Zhang
2018-01-15 13:14 ` Jia Zhang
2018-01-15 9:59 ` [PATCH 0/2] " Borislav Petkov
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=20180115100740.emrdb6u4b75ixkbj@pd.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=zhang.jia@linux.alibaba.com \
/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
all inboxes | Powered by JetHome®