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 0/2] x86/microcode/intel: Extend BDW late-loading with platform id and LLC check
Date: Mon, 15 Jan 2018 10:59:43 +0100 [thread overview]
Message-ID: <20180115095943.mzd3bagx2vqapm34@pd.tnic> (raw)
In-Reply-To: <1515995003-113069-1-git-send-email-zhang.jia@linux.alibaba.com>
On Mon, Jan 15, 2018 at 01:43:21PM +0800, Jia Zhang wrote:
> The fix further reduces the impact for the BDW model which has to launch
> a machine reset in order to run microcode update in BIOS. This point is
> important for some vendors without the concern about machine reboot in
> order to fix up Spectre v2.
That's a ridiculous excuse - those vendors need to reboot to get these
fixes first. So what is the real reason?
Why can't they simply move to early loading like the rest of the world?
So srsly, how many times are we going to fix this erratum? Are you going
to come up with yet another fix *after* this one?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2018-01-15 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 5:43 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
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 ` Borislav Petkov [this message]
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=20180115095943.mzd3bagx2vqapm34@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®