From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753834AbcADXQ4 (ORCPT <rfc822;w@1wt.eu>);
	Mon, 4 Jan 2016 18:16:56 -0500
Received: from mail.skyhub.de ([78.46.96.112]:58584 "EHLO mail.skyhub.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752012AbcADXQy (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 4 Jan 2016 18:16:54 -0500
Date: Tue, 5 Jan 2016 00:16:33 +0100
From: Borislav Petkov <bp@alien8.de>
To: Piotr =?utf-8?Q?D=C4=85browski?= <ultr@ultr.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new cmdline parameter disable_cpu_features= (microcode update?)
Message-ID: <20160104231633.GA15949@pd.tnic>
References: <CAEApFrjBJggQg+94ak9usynEgZhGPZwo7F+Dz6tPu45mc4XdnQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAEApFrjBJggQg+94ak9usynEgZhGPZwo7F+Dz6tPu45mc4XdnQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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.