[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<172548183128.1158691.9881712792582282151.git-patchwork-notify@kernel.org>
Date: Wed, 04 Sep 2024 20:30:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Pu Lehui <pulehui@...weicloud.com>
Cc: bpf@...r.kernel.org, linux-riscv@...ts.infradead.org,
netdev@...r.kernel.org, andrii@...nel.org, bjorn@...nel.org,
iii@...ux.ibm.com, ast@...nel.org, daniel@...earbox.net,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org, puranjay@...nel.org,
palmer@...belt.com, pulehui@...wei.com
Subject: Re: [PATCH bpf-next v3 0/4] Fix accessing first syscall argument on RV64
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Sat, 31 Aug 2024 04:19:30 +0000 you 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]
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/4] libbpf: Access first syscall argument with CO-RE direct read on s390
https://git.kernel.org/bpf/bpf-next/c/65ee11d9c822
- [bpf-next,v3,2/4] libbpf: Access first syscall argument with CO-RE direct read on arm64
https://git.kernel.org/bpf/bpf-next/c/ebd8ad474888
- [bpf-next,v3,3/4] selftests/bpf: Enable test_bpf_syscall_macro:syscall_arg1 on s390 and arm64
https://git.kernel.org/bpf/bpf-next/c/3a913c4d62e1
- [bpf-next,v3,4/4] libbpf: Fix accessing first syscall argument on RV64
https://git.kernel.org/bpf/bpf-next/c/13143c5816bc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists