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 ; 12 Dec 2018 22:40:56 -0000 Received: from aserp2130.oracle.com ([141.146.126.79]) by Galois.linutronix.de with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gXDBX-0003Ji-9S for speck@linutronix.de; Wed, 12 Dec 2018 23:40:55 +0100 Received: from pps.filterd (aserp2130.oracle.com [127.0.0.1]) by aserp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wBCMdZUo141990 for ; Wed, 12 Dec 2018 22:40:49 GMT Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp2130.oracle.com with ESMTP id 2pawwp4grm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 12 Dec 2018 22:40:48 +0000 Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id wBCMem07030806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 12 Dec 2018 22:40:48 GMT Received: from abhmp0019.oracle.com (abhmp0019.oracle.com [141.146.116.25]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id wBCMelwb000322 for ; Wed, 12 Dec 2018 22:40:48 GMT Date: Wed, 12 Dec 2018 17:40:47 -0500 From: Konrad Rzeszutek Wilk Subject: [MODERATED] Re: [PATCH v2 2/8] MDSv2 1 Message-ID: <20181212224046.GF7946@char.us.oracle.com> References: <87784B01-00DE-4E4E-AF13-7CEFC9903019@oracle.com> <20181211100335.GB25994@zn.tnic> <20181212213147.GR9077@char.us.oracle.com> <20181212221731.GF6696@zn.tnic> MIME-Version: 1.0 In-Reply-To: <20181212221731.GF6696@zn.tnic> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Wed, Dec 12, 2018 at 11:17:31PM +0100, speck for Borislav Petkov wrote: > On Wed, Dec 12, 2018 at 04:31:48PM -0500, speck for Konrad Rzeszutek Wilk wrote: > > We can start that conversation upstream, but Thomas and Boris -are you > > guys very much against this idea with the upstream kernel or would you > > be up for taking a sip from this can? > > Well, I'm willing to hear your arguments for why you absolutely must > load microcode during runtime, without rebooting and cannot bundle a > microcode upgrade with a kernel upgrade and do a normal reboot during > scheduled system downtime. That is easy - "cloud" - you know $X billion market where everybody decides that 99.99999% is needed which means you can only reboot for 1 second.