From: Borislav Petkov <bp@alien8.de>
To: "Piotr Dąbrowski" <ultr@ultr.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new cmdline parameter disable_cpu_features= (microcode update?)
Date: Tue, 5 Jan 2016 00:16:33 +0100 [thread overview]
Message-ID: <20160104231633.GA15949@pd.tnic> (raw)
In-Reply-To: <CAEApFrjBJggQg+94ak9usynEgZhGPZwo7F+Dz6tPu45mc4XdnQ@mail.gmail.com>
On Mon, Jan 04, 2016 at 11:55:57PM +0100, Piotr Dąbrowski wrote:
> Is such thing even possible? And would it be a reasonable thing to do
> (maybe the rest of the microcode would break badly without the factory
> flags set)?
You cannot change the microcode patches - they're supplied by the CPU
vendors as is and are signed/encrypted.
In an ideal world, we should have BIOS disable options for all CPU
features which could turn out to be problematic so that the user remains
in control. Without the need to be applying microcode patches even.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-01-04 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 22:55 new cmdline parameter disable_cpu_features= (microcode update?) Piotr Dąbrowski
2016-01-04 23:16 ` Borislav Petkov [this message]
2016-01-05 0:27 ` Piotr Dąbrowski
2016-01-05 11:38 ` 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=20160104231633.GA15949@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ultr@ultr.pl \
/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