diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2021-04-14 15:45:43 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-06-03 09:38:10 +0300 |
| commit | 2191a85943ca848ec756ad79623774d2116a3be4 (patch) | |
| tree | 7871f998b5cd80d861a2f59657096368239db9a4 /fs/btrfs | |
| parent | 8f9221c442a38d2efc08d6c15d1287dbc95e6c87 (diff) | |
| download | linux-2191a85943ca848ec756ad79623774d2116a3be4.tar.xz | |
openrisc: Define memory barrier mb
[ Upstream commit 8b549c18ae81dbc36fb11e4aa08b8378c599ca95 ]
This came up in the discussion of the requirements of qspinlock on an
architecture. OpenRISC uses qspinlock, but it was noticed that the
memmory barrier was not defined.
Peter defined it in the mail thread writing:
As near as I can tell this should do. The arch spec only lists
this one instruction and the text makes it sound like a completion
barrier.
This is correct so applying this patch.
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
[shorne@gmail.com:Turned the mail into a patch]
Signed-off-by: Stafford Horne <shorne@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/btrfs')
0 files changed, 0 insertions, 0 deletions