From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 11 Dec 2018 10:03:54 -0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gWetM-00007J-9W for speck@linutronix.de; Tue, 11 Dec 2018 11:03:53 +0100 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 11E89ACD1 for ; Tue, 11 Dec 2018 10:03:46 +0000 (UTC) Date: Tue, 11 Dec 2018 11:03:35 +0100 From: Borislav Petkov Subject: [MODERATED] Re: [PATCH v2 2/8] MDSv2 1 Message-ID: <20181211100335.GB25994@zn.tnic> References: <87784B01-00DE-4E4E-AF13-7CEFC9903019@oracle.com> MIME-Version: 1.0 In-Reply-To: <87784B01-00DE-4E4E-AF13-7CEFC9903019@oracle.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Mon, Dec 10, 2018 at 07:13:18PM -0500, speck for Kanth Ghatraju wrote: > If you have a patched kernel but old microcode and then do a late load > of the microcode, And to extend what the others said: late microcode loading is a can of worms which we shouldnt've opened back then. Especially since it requires a complicated dance on the OS part to quiesce the cores to even work without locking up the core or whatever crazy can happen. So microcode update should be handled just like updating your kernel - you need to reboot the machine. --=20 Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Jane Smithard, Graham Norton, HR= B 21284 (AG N=C3=BCrnberg) --=20