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 ; 09 Jan 2019 17:33:44 -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 1ghHjZ-00067S-PV for speck@linutronix.de; Wed, 09 Jan 2019 18:33:43 +0100 Date: Wed, 9 Jan 2019 09:33:38 -0800 From: Andi Kleen Subject: [MODERATED] Re: qemu patch for mb_clear Message-ID: <20190109173338.GQ6118@tassilo.jf.intel.com> References: <20181221003101.GA32181@tassilo.jf.intel.com> <20190109170919.GU23427@char.us.oracle.com> MIME-Version: 1.0 In-Reply-To: <20190109170919.GU23427@char.us.oracle.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Wed, Jan 09, 2019 at 12:09:19PM -0500, speck for Konrad Rzeszutek Wilk wrote: > On Thu, Dec 20, 2018 at 04:31:01PM -0800, speck for Andi Kleen wrote: > > > > For reference here is the qemu patch needed for using MB_CLEAR in a KVM > > guest. > > I thought it was called 'MD_CLEAR' ? So far it's still called MB_CLEAR in the white papers AFAIK. -Andi