From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, jiangfeng@kylinos.cn,
bjorn@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
puranjay@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
alex@ghiti.fr, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v5 0/3] Add bpf stack arguments support for RV64
Date: Sun, 06 Sep 2026 14:30:20 +0000 [thread overview]
Message-ID: <178870502013.1578634.1317677297595952017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260905085857.14143-1-pulehui@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Sat, 5 Sep 2026 08:58:54 +0000 you wrote:
> Implement bpf_jit_supports_stack_args() on RV64 JIT to allow bpf
> subprogs and kfuncs to pass and receive more than 5 arguments.
>
> Tested on riscv64 QEMU with LLVM main [1]; BPF-to-BPF and kfunc
> selftests pass.
>
> [1] https://github.com/llvm/llvm-project/pull/189060
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] riscv, bpf: Remap BPF_REG_0 and RV_REG_TCC
https://git.kernel.org/bpf/bpf-next/c/f80a09c486e7
- [bpf-next,v5,2/3] riscv, bpf: Add BPF stack arguments support for RV64 JIT
https://git.kernel.org/bpf/bpf-next/c/ba754185f902
- [bpf-next,v5,3/3] selftests/bpf: Enable stack argument tests for RV64
https://git.kernel.org/bpf/bpf-next/c/7687f1cbbaf8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, jiangfeng@kylinos.cn,
bjorn@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
puranjay@kernel.org, pjw@kernel.org, palmer@dabbelt.com,
alex@ghiti.fr, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v5 0/3] Add bpf stack arguments support for RV64
Date: Sun, 06 Sep 2026 14:30:20 +0000 [thread overview]
Message-ID: <178870502013.1578634.1317677297595952017.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260905085857.14143-1-pulehui@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Sat, 5 Sep 2026 08:58:54 +0000 you wrote:
> Implement bpf_jit_supports_stack_args() on RV64 JIT to allow bpf
> subprogs and kfuncs to pass and receive more than 5 arguments.
>
> Tested on riscv64 QEMU with LLVM main [1]; BPF-to-BPF and kfunc
> selftests pass.
>
> [1] https://github.com/llvm/llvm-project/pull/189060
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] riscv, bpf: Remap BPF_REG_0 and RV_REG_TCC
https://git.kernel.org/bpf/bpf-next/c/f80a09c486e7
- [bpf-next,v5,2/3] riscv, bpf: Add BPF stack arguments support for RV64 JIT
https://git.kernel.org/bpf/bpf-next/c/ba754185f902
- [bpf-next,v5,3/3] selftests/bpf: Enable stack argument tests for RV64
https://git.kernel.org/bpf/bpf-next/c/7687f1cbbaf8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-06 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 8:58 [PATCH bpf-next v5 0/3] Add bpf stack arguments support for RV64 Pu Lehui
2026-09-05 8:58 ` Pu Lehui
2026-09-05 8:58 ` [PATCH bpf-next v5 1/3] riscv, bpf: Remap BPF_REG_0 and RV_REG_TCC Pu Lehui
2026-09-05 8:58 ` Pu Lehui
2026-09-05 9:42 ` bot+bpf-ci
2026-09-05 9:42 ` bot+bpf-ci
2026-09-05 9:56 ` Pu Lehui
2026-09-05 9:56 ` Pu Lehui
2026-09-05 8:58 ` [PATCH bpf-next v5 2/3] riscv, bpf: Add BPF stack arguments support for RV64 JIT Pu Lehui
2026-09-05 8:58 ` Pu Lehui
2026-09-05 8:58 ` [PATCH bpf-next v5 3/3] selftests/bpf: Enable stack argument tests for RV64 Pu Lehui
2026-09-05 8:58 ` Pu Lehui
2026-09-05 9:03 ` sashiko-bot
2026-09-05 9:46 ` Pu Lehui
2026-09-06 14:22 ` [PATCH bpf-next v5 0/3] Add bpf stack arguments support " Björn Töpel
2026-09-06 14:22 ` Björn Töpel
2026-09-06 14:30 ` patchwork-bot+netdevbpf [this message]
2026-09-06 14:30 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178870502013.1578634.1317677297595952017.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jiangfeng@kylinos.cn \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.