From: Jia Zhang <zhang.jia@linux.alibaba.com>
To: Borislav Petkov <bp@alien8.de>, tony.luck@intel.com
Cc: hmh@hmh.eng.br, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check
Date: Tue, 16 Jan 2018 09:14:44 +0800 [thread overview]
Message-ID: <2ddaecd3-c121-cb37-219e-0e7b1d17c22e@linux.alibaba.com> (raw)
In-Reply-To: <20180115184616.r6pypjegywyd7ncm@pd.tnic>
在 2018/1/16 上午2:46, Borislav Petkov 写道:
> On Mon, Jan 15, 2018 at 09:11:57PM +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.
>> Actually, the impact can be reduced further through adding the checks
>> for the size of LLC per core.
>>
>> For more details, see erratum BDF90 in document #334165 (Intel Xeon
>> Processor E7-8800/4800 v4 Product Family Specification Update) from
>> September 2017.
>>
>> Signed-off-by: Jia Zhang <zhang.jia@linux.alibaba.com>
>> ---
>> arch/x86/kernel/cpu/microcode/intel.c | 15 +++++++++++++--
>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kernel/cpu/microcode/intel.c b/arch/x86/kernel/cpu/microcode/intel.c
>> index d9e460f..9143cf2 100644
>> --- a/arch/x86/kernel/cpu/microcode/intel.c
>> +++ b/arch/x86/kernel/cpu/microcode/intel.c
>> @@ -906,18 +906,29 @@ static int get_ucode_fw(void *to, const void *from, size_t n)
>> return 0;
>> }
>>
>> +static int llc_size_per_core(struct cpuinfo_x86 *c)
>> +{
>> + u64 llc_size = c->x86_cache_size * 1024;
>> +
>> + do_div(llc_size, c->x86_max_cores);
>
> This is done per-CPU - I don't want it to do the same division for each
> core. Do it once at driver init only for that model and cache it.
How about this?
--- a/arch/x86/kernel/cpu/microcode/intel.c
+++ b/arch/x86/kernel/cpu/microcode/intel.c
@@ -908,10 +908,13 @@ static int get_ucode_fw(void *to, const void
*from, size_t n)
static int llc_size_per_core(struct cpuinfo_x86 *c)
{
- u64 llc_size = c->x86_cache_size * 1024;
-
- do_div(llc_size, c->x86_max_cores);
+ static u64 llc_size;
+ if (unlikely(!llc_size)) {
+ llc_size = c->x86_cache_size * 1024;
+ do_div(llc_size, c->x86_max_cores);
+ }
+
return (int)llc_size;
}
or driver init style?
@@ -996,5 +999,7 @@ struct microcode_ops * __init init_intel_microcode(void)
return NULL;
}
+ llc_size_per_core = calc_llc_size_per_core(c);
+
return µcode_intel_ops;
}
or more generic?
@@ -984,6 +987,7 @@ static int get_ucode_user(void *to, const void
*from, size_t n)
.request_microcode_fw = request_microcode_fw,
.collect_cpu_info = collect_cpu_info,
.apply_microcode = apply_microcode_intel,
+ .is_blacklisted = is_blacklisted,
};
>
>> +
>> + return (int)llc_size;
>> +}
>> +
>> static bool is_blacklisted(unsigned int cpu)
>> {
>> struct cpuinfo_x86 *c = &cpu_data(cpu);
>>
>> /*
>> * Late loading on model 79 with microcode revision less than 0x0b000021
>> - * may result in a system hang. This behavior is documented in item
>> - * BDF90, #334165 (Intel Xeon Processor E7-8800/4800 v4 Product Family).
>> + * and LLC size per core bigger than 2.5MB may result in a system hang.
>> + * This behavior is documented in item BDF90, #334165 (Intel Xeon
>> + * Processor E7-8800/4800 v4 Product Family).
>> */
>> if (c->x86 == 6 &&
>> c->x86_model == INTEL_FAM6_BROADWELL_X &&
>> c->x86_mask == 0x01 &&
>> + llc_size_per_core(c) > 2621440 &&
>
> I'm not taking this: this looks like a bunch of voodoo magic numbers.
> Please get someone from Intel to explain first.
Tony, could you clarify this?
Thanks,
Jia
>
next prev parent reply other threads:[~2018-01-16 1:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 13:11 Jia Zhang
2018-01-15 18:46 ` Borislav Petkov
2018-01-16 1:14 ` Jia Zhang [this message]
2018-01-16 14:59 ` Borislav Petkov
2018-01-16 17:02 ` Luck, Tony
2018-01-16 17:24 ` Luck, Tony
2018-01-16 20:01 ` Borislav Petkov
2018-01-16 20:11 ` Luck, Tony
2018-01-16 20:50 ` Borislav Petkov
2018-01-16 21:30 ` Luck, Tony
2018-01-16 21:51 ` Borislav Petkov
2018-01-19 0:27 ` Jia Zhang
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=2ddaecd3-c121-cb37-219e-0e7b1d17c22e@linux.alibaba.com \
--to=zhang.jia@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=hmh@hmh.eng.br \
--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®