Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753870AbeAGNGW (ORCPT + 1 other); Sun, 7 Jan 2018 08:06:22 -0500 Received: from foss.arm.com ([217.140.101.70]:57876 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753283AbeAGNGU (ORCPT ); Sun, 7 Jan 2018 08:06:20 -0500 Date: Sun, 7 Jan 2018 13:06:11 +0000 From: Mark Rutland To: Randy Dunlap Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, dan.j.williams@intel.com, elena.reshetova@intel.com, corbet@lwn.net, alan@linux.intel.com, peterz@infradead.org, will.deacon@arm.com, gregkh@linuxfoundation.org, tglx@linutronix.de, Paul Turner Subject: Re: [RFCv2 2/4] Documentation: document nospec helpers Message-ID: <20180107130610.3vllt5cm2b3orukd@salmiak> References: <20180105145750.53294-1-mark.rutland@arm.com> <20180105145750.53294-3-mark.rutland@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Sat, Jan 06, 2018 at 09:20:59PM -0800, Randy Dunlap wrote: > On 01/05/18 06:57, Mark Rutland wrote: > > Document the rationale and usage of the new nospec*() helpers. > > > > Signed-off-by: Mark Rutland > > Signed-off-by: Will Deacon > > Cc: Dan Williams > > Cc: Jonathan Corbet > > Cc: Peter Zijlstra > > --- > > Documentation/speculation.txt | 166 ++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 166 insertions(+) > > create mode 100644 Documentation/speculation.txt > > > > diff --git a/Documentation/speculation.txt b/Documentation/speculation.txt > > new file mode 100644 > > index 000000000000..748fcd4dcda4 > > --- /dev/null > > +++ b/Documentation/speculation.txt > > @@ -0,0 +1,166 @@ > > + > > +Typically speculative execution cannot be observed from architectural state, > > +such as the contents of registers. However, in some cases it is possible to > > +observe its impact on microarchitectural state, such as the presence or > > +absence of data in caches. Such state may form side-channels which can be > > +observed to extract secret information. > > I'm curious about what it takes to observe this... > > or is that covered in the exploit papers? That's covered elsewhere, e.g. https://googleprojectzero.blogspot.co.uk/2018/01/reading-privileged-memory-with-side.html I'll add some references. Thanks, Mark.