aboutsummaryrefslogtreecommitdiffstats
path: root/net/bpf
diff options
context:
space:
mode:
authorDaniel Borkmann <daniel@iogearbox.net>2019-04-09 11:44:46 +0200
committerAlexei Starovoitov <ast@kernel.org>2019-04-11 14:45:50 -0700
commit6b7a21140fca461c6d8d5c65a3746e7da50a409e (patch)
tree460753960398fedf6a942e734c59e5b07d0c00f7 /net/bpf
parentMerge branch 'bpf-l2-encap' (diff)
downloadlinux-dev-6b7a21140fca461c6d8d5c65a3746e7da50a409e.tar.xz
linux-dev-6b7a21140fca461c6d8d5c65a3746e7da50a409e.zip
tools: add smp_* barrier variants to include infrastructure
Add the definition for smp_rmb(), smp_wmb(), and smp_mb() to the tools include infrastructure: this patch adds the implementation for x86-64 and arm64, and have it fall back as currently is for other archs which do not have it implemented at this point. The x86-64 one uses lock + add combination for smp_mb() with address below red zone. This is on top of 09d62154f613 ("tools, perf: add and use optimized ring_buffer_{read_head, write_tail} helpers"), which didn't touch smp_* barrier implementations. Magnus recently rightfully reported however that the latter on x86-64 still wrongly falls back to sfence, lfence and mfence respectively, thus fix that for applications under tools making use of these to avoid such ugly surprises. The main header under tools (include/asm/barrier.h) will in that case not select the fallback implementation. Reported-by: Magnus Karlsson <magnus.karlsson@intel.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'net/bpf')
0 files changed, 0 insertions, 0 deletions