Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 14 Nov 2018 02:32:53 -0000 Received: from mga07.intel.com ([134.134.136.100]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gMkz5-0002Kh-4y for speck@linutronix.de; Wed, 14 Nov 2018 03:32:52 +0100 Date: Tue, 13 Nov 2018 18:32:47 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH 2/4] RFC-MDSv1 0 Message-ID: <20181114023247.GK6218@tassilo.jf.intel.com> 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 Tue, Nov 13, 2018 at 09:47:57PM +0100, speck for Jiri Kosina wrote: > On Sun, 11 Nov 2018, speck for Andi Kleen wrote: > > > We don't need to do this for guests because the L1TF cache flush will > > implicitely do the same flushing, and is automatically selected on MDS > > affected systems. > > Just to make sure, as there has been some confusion around this last time > this has been discussed -- for the above to be true, ucode update is > necessary anyway, right? The L1D flush, as implemented in the current > publicly available ucode, doesn't flush the microarchitectural buffers, > that is only coming with ucode that will provide enhanced verw semantics, > right? Yes that is correct. -Andi