[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f7a7d089-3313-4c25-884c-8d073ddf54e4@huawei.com>
Date: Thu, 29 Aug 2024 21:35:20 +0800
From: Pu Lehui <pulehui@...wei.com>
To: Pu Lehui <pulehui@...weicloud.com>, <bpf@...r.kernel.org>,
<linux-riscv@...ts.infradead.org>, <netdev@...r.kernel.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>, Andrii Nakryiko <andrii@...nel.org>, 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>
Subject: Re: [PATCH bpf-next 0/2] Fix accessing first syscall argument on RV64
On 2024/8/29 21:32, Pu Lehui wrote:
> 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 (2):
> libbpf: Fix accessing first syscall argument on RV64
> selftests/bpf: Skip case involving first arg in bpf_syscall_macro on
> RV64
>
> tools/lib/bpf/bpf_tracing.h | 9 ++++++++-
> .../selftests/bpf/prog_tests/test_bpf_syscall_macro.c | 2 +-
> tools/testing/selftests/bpf/progs/bpf_syscall_macro.c | 2 +-
> 3 files changed, 10 insertions(+), 3 deletions(-)
>
There was an error in sending this time. A new one has been sent. Sorry
for the noise.
Powered by blists - more mailing lists