Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 13 Feb 2019 22:33:42 -0000 Received: from youngberry.canonical.com ([91.189.89.112]) by Galois.linutronix.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1gu365-0007Aa-8W for speck@linutronix.de; Wed, 13 Feb 2019 23:33:41 +0100 Received: from 162-237-133-238.lightspeed.rcsntx.sbcglobal.net ([162.237.133.238] helo=lindsey) by youngberry.canonical.com with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1gu35z-0000ib-Ei for speck@linutronix.de; Wed, 13 Feb 2019 22:33:35 +0000 Date: Wed, 13 Feb 2019 16:33:32 -0600 From: Tyler Hicks Subject: [MODERATED] Re: [PATCH v5 00/27] MDSv5 19 Message-ID: <20190213223332.GL4516@lindsey> References: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On 2019-01-28 12:34:38, speck for Thomas Gleixner wrote: > Andi, > > On Fri, 18 Jan 2019, speck for Andi Kleen wrote: > > can you please split this into two patch series: > > 1) The initial mitigation > > 2) The conditional mode Andi, I know you've been busy with the PERF changes but I'm curious if you plan to split up this series, as requested by Thomas? Intel is starting to ask software vendors when they might have beta builds of the mitigations available and my answer is going to depend on whether or not this split is going to be available soon. Additionally, I can't seem to find the mbox of MDSv5. If you already sent it, could you point out the message ID? Thanks! Tyler