mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jia Zhang <qianyue.zj@alibaba-inc.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	tony.luck@intel.com
Subject: Re: [PATCH v4] x86/microcode/intel: Blacklist the specific BDW-EP for late loading
Date: Fri, 29 Dec 2017 14:44:39 +0100	[thread overview]
Message-ID: <20171229134439.GA19010@nazgul.tnic> (raw)
In-Reply-To: <492a0fe6-ca0b-ca97-27bf-e6407c60469c@alibaba-inc.com>

On Fri, Dec 29, 2017 at 09:17:34PM +0800, Jia Zhang wrote:
> Namely, the end user has to make a BIOS update to uprev the microcode.

Not quite: end user is dependent on the OEM to get a BIOS update.

What is meant with early loading in this context is, to put the
microcode in the initrd so that it gets loaded very early during the
*kernel* boot. And early-initrd-based loading is the default method we
do microcode loading with, anyway.

So the blacklisting is only for *late* loading, through the sysfs
trigger. Which is only there for historical reasons and for some
configurations.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2017-12-29 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 12:42 Jia Zhang
2017-12-27  4:52 ` Luck, Tony
2017-12-28 12:24 ` Ingo Molnar
2017-12-28 13:23   ` Jia Zhang
2017-12-29 12:48     ` Ingo Molnar
2017-12-29 13:17       ` Jia Zhang
2017-12-29 13:44         ` Borislav Petkov [this message]
2017-12-29 14:12           ` Jia Zhang
2017-12-29 14:40             ` 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=20171229134439.GA19010@nazgul.tnic \
    --to=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=qianyue.zj@alibaba-inc.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

Powered by JetHome