From: "H. Peter Anvin" <hpa@zytor.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Borislav Petkov <bp@alien8.de>, Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: early microcode: how to disable at runtime?
Date: Sun, 31 Aug 2014 12:48:23 -0700 [thread overview]
Message-ID: <54037C07.8060703@zytor.com> (raw)
In-Reply-To: <20140831194548.GA12628@khazad-dum.debian.net>
On 08/31/2014 12:45 PM, Henrique de Moraes Holschuh wrote:
> Currently, there is no way to disable early microcode update at runtime. If
> an early initramfs with microcode update data is available, it will always
> be used.
>
> This can be a very big deal when things go wrong: it is hard for the regular
> user to recover from an initramfs image that crashes the system, and the
> early initramfs has no "disable" trigger.
>
> In the general case, booting from rescue media will be required to fix the
> system.
>
> Unfortunately, the BSP microcode update is handled before early_param() is
> available, so a kernel command line parameter to disable early microcode
> updates for the BSP isn't easily possible.
>
> Other than duplicating much of the code in parse_early_param/parse_args to
> search for a "noearlymcu" parameter, is there any other way we could add a
> disable switch for the early microcode update system?
>
Probably more like something more like arch/x86/boot/cmdline.c. Maybe
we could even make it sharable.
-hpa
next prev parent reply other threads:[~2014-08-31 19:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 23:19 BUG: early intel microcode update violating alignment rules Henrique de Moraes Holschuh
2014-08-11 10:22 ` Borislav Petkov
2014-08-11 13:16 ` Henrique de Moraes Holschuh
2014-08-11 14:00 ` Borislav Petkov
2014-08-11 14:50 ` H. Peter Anvin
2014-08-11 18:52 ` Bill Davidsen
2014-08-11 19:15 ` Borislav Petkov
2014-08-14 13:12 ` Henrique de Moraes Holschuh
2014-08-11 14:51 ` H. Peter Anvin
2014-08-11 18:18 ` Henrique de Moraes Holschuh
2014-08-11 18:48 ` H. Peter Anvin
2014-08-31 19:45 ` early microcode: how to disable at runtime? Henrique de Moraes Holschuh
2014-08-31 19:48 ` H. Peter Anvin [this message]
2014-08-31 20:11 ` Henrique de Moraes Holschuh
2014-09-01 5:13 ` Borislav Petkov
2014-09-01 10:19 ` Henrique de Moraes Holschuh
2014-09-01 16:35 ` H. Peter Anvin
2014-09-01 17:43 ` Henrique de Moraes Holschuh
2014-09-01 18:48 ` H. Peter Anvin
2014-09-01 19:59 ` Henrique de Moraes Holschuh
2014-09-02 6:33 ` Borislav Petkov
2014-09-02 13:16 ` Henrique de Moraes Holschuh
2014-09-03 6:40 ` Borislav Petkov
2014-09-03 12:43 ` Henrique de Moraes Holschuh
2014-09-04 15:42 ` Borislav Petkov
2014-09-04 17:45 ` Henrique de Moraes Holschuh
2014-09-05 8:50 ` Borislav Petkov
2014-09-05 14:23 ` Henrique de Moraes Holschuh
2014-09-04 18:37 ` Yu, Fenghua
2014-09-05 8:52 ` 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=54037C07.8060703@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.