From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ak@linux.intel.com>
Received: from mga14.intel.com ([192.55.52.115])
	by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80)
	(envelope-from <ak@linux.intel.com>)
	id 1fGu0H-0005IW-Lg
	for speck@linutronix.de; Fri, 11 May 2018 00:25:38 +0200
Date: Thu, 10 May 2018 15:25:33 -0700
From: Andi Kleen <ak@linux.intel.com>
Subject: [MODERATED] Re: [patch V11 05/16] SSB 5
Message-ID: <20180510222533.GH13616@tassilo.jf.intel.com>
References: <20180502215102.192655950@linutronix.de>
 <20180502215416.459915781@linutronix.de>
 <20180510175257.GD13616@tassilo.jf.intel.com>
 <20180510183058.GJ27358@char.us.oracle.com>
 <20180510190850.GE13616@tassilo.jf.intel.com>
 <20180510212232.GT27358@char.us.oracle.com>
MIME-Version: 1.0
In-Reply-To: <20180510212232.GT27358@char.us.oracle.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: speck@linutronix.de
List-ID: <speck.linutronix.de>

> It is actually slower. I tried doing it last time with the spectre/meltdown
> and the performance was way slower than doing it this way. I can dig up the patches
>  - as I think we did the tests on Broadwell but hadn't tried Skylake or such
> (or maybe it was the other way around).

Was this with MSR lists unconditionally, or with MSR list combined with 
the "wait for the first write" approach?

-Andi