Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1301181
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: new cmdline parameter disable_cpu_features= (microcode update?) |
| Date | 2016-01-05 00:20 +0100 |
| Message-ID | <qNmzU-1JR-13@gated-at.bofh.it> (permalink) |
| References | <qNmgy-1m8-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
new cmdline parameter disable_cpu_features= (microcode update?) Piotr Dąbrowski <ultr@ultr.pl> - 2016-01-05 00:00 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Borislav Petkov <bp@alien8.de> - 2016-01-05 00:20 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Piotr Dąbrowski <ultr@ultr.pl> - 2016-01-05 01:30 +0100
Re: new cmdline parameter disable_cpu_features= (microcode update?) Borislav Petkov <bp@alien8.de> - 2016-01-05 12:40 +0100
csiph-web