From: Jia Zhang <zhang.jia@linux.alibaba.com>
To: Borislav Petkov <bp@alien8.de>
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 2/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check
Date: Mon, 15 Jan 2018 21:06:07 +0800 [thread overview]
Message-ID: <31061762-96f4-0cf7-077a-56c422088bea@linux.alibaba.com> (raw)
In-Reply-To: <20180115101016.k4ksjlclufogcfrt@pd.tnic>
Yes I'm wrong with platform id so drop it.
Jia
在 2018/1/15 下午6:10, Borislav Petkov 写道:
> On Mon, Jan 15, 2018 at 01:43:23PM +0800, Jia Zhang wrote:
>> The commit b94b73733171
>> ("x86/microcode/intel: Extend BDW late-loading with a revision check")
>> reduces the impact of erratum BDF90 for Broadwell process model. Now,
>> the impact can be reduced further through adding the checks for
>> platform id and the size of LLC per core.
>>
>> This fix is useful to reduce the impact for microcode update launched
>> by BIOS with a must machine reset.
>>
>> For more details, see erratum BDF90 in document #334165 (Intel Xeon
>> Processor E7-8800/4800 v4 Product Family Specification Update) from
>> September 2017.
>
> You must be looking at something NDA or so but this:
>
> https://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e7-v4-spec-update.pdf
>
> doesn't have none of that
>
>> + llc_size_per_core(c) > 2621440 &&
>> + c->platform_id == 0xef &&
>
> fun.
>
next prev parent reply other threads:[~2018-01-15 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 5:43 [PATCH 0/2] " Jia Zhang
2018-01-15 5:43 ` [PATCH 1/2] x86/intel: introduce platform_id Jia Zhang
2018-01-15 10:07 ` Borislav Petkov
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 [this message]
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=31061762-96f4-0cf7-077a-56c422088bea@linux.alibaba.com \
--to=zhang.jia@linux.alibaba.com \
--cc=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 \
/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®