[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240831023646.1558629-1-pulehui@huaweicloud.com>
Date: Sat, 31 Aug 2024 02:36:42 +0000
From: Pu Lehui <pulehui@...weicloud.com>
To: bpf@...r.kernel.org,
linux-riscv@...ts.infradead.org,
netdev@...r.kernel.org,
Andrii Nakryiko <andrii@...nel.org>
Cc: Björn Töpel <bjorn@...nel.org>,
Ilya Leoshkevich <iii@...ux.ibm.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>,
Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>,
Puranjay Mohan <puranjay@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>,
Pu Lehui <pulehui@...wei.com>
Subject: [PATCH bpf-next v2 0/4] Fix accessing first syscall argument on RV64
On RV64, as Ilya mentioned before [0], the first syscall parameter should be
accessed through orig_a0 (see arch/riscv64/include/asm/syscall.h),
otherwise it will cause selftests like bpf_syscall_macro, vmlinux,
test_lsm, etc. to fail on RV64.
Link: https://lore.kernel.org/bpf/20220209021745.2215452-1-iii@linux.ibm.com [0]
Pu Lehui (4):
libbpf: Access first syscall argument with CO-RE direct read on s390
libbpf: Access first syscall argument with CO-RE direct read on arm64
selftests/bpf: Enable test_bpf_syscall_macro:syscall_arg1 on s390 and
arm64
libbpf: Fix accessing first syscall argument on RV64
tools/lib/bpf/bpf_tracing.h | 17 ++++++++++++-----
.../bpf/prog_tests/test_bpf_syscall_macro.c | 4 ----
2 files changed, 12 insertions(+), 9 deletions(-)
--
2.34.1
Powered by blists - more mailing lists