[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <40zxfm40PKz9s0w@ozlabs.org>
Date: Tue, 5 Jun 2018 00:10:39 +1000 (AEST)
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Michael Ellerman <mpe@...erman.id.au>, linuxppc-dev@...abs.org
Cc: msuchanek@...e.de, linux-kernel@...r.kernel.org, npiggin@...il.com
Subject: Re: [1/6] powerpc/64s: Add barrier_nospec
On Tue, 2018-04-24 at 04:15:54 UTC, Michael Ellerman wrote:
> From: Michal Suchanek <msuchanek@...e.de>
>
> A no-op form of ori (or immediate of 0 into r31 and the result stored
> in r31) has been re-tasked as a speculation barrier. The instruction
> only acts as a barrier on newer machines with appropriate firmware
> support. On older CPUs it remains a harmless no-op.
>
> Implement barrier_nospec using this instruction.
>
> mpe: The semantics of the instruction are believed to be that it
> prevents execution of subsequent instructions until preceding branches
> have been fully resolved and are no longer executing speculatively.
> There is no further documentation available at this time.
>
> Signed-off-by: Michal Suchanek <msuchanek@...e.de>
> Signed-off-by: Michael Ellerman <mpe@...erman.id.au>
Series applied to powerpc next.
https://git.kernel.org/powerpc/c/a6b3964ad71a61bb7c61d80a60bea7
cheers
Powered by blists - more mailing lists