From: patchwork-bot+netdevbpf@kernel.org
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
memxor@gmail.com, bjorn@kernel.org, puranjay@kernel.org,
ihor.solodrai@linux.dev, eddyz87@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, pulehui@huawei.com, pjw@kernel.org,
palmer@dabbelt.com, shuah@kernel.org, guoren@kernel.org,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] bpf, riscv: Add support for signed arena loads
Date: Tue, 25 Aug 2026 13:30:09 +0000 [thread overview]
Message-ID: <178766460914.3460835.2556196507996630304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1787140923.git.cp0613@linux.alibaba.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 19 Aug 2026 20:09:22 +0800 you wrote:
> Hi,
>
> Signed loads from arena memory are currently unsupported on riscv64:
> bpf_jit_supports_insn() rejects BPF_MEMSX loads when in_arena is set,
> so the verifier fails such programs with "sign extending loads from
> arena are not supported yet". The x86 and arm64 JITs gained support
> for them in v6.18 (a91ae3c89311, eab2a71f3a6a). Since compilers are
> free to generate signed loads into arena memory (e.g. GCC-14 was
> reported to do so), otherwise valid BPF programs fail to load on
> riscv64.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf, riscv: Add support for signed arena loads
https://git.kernel.org/bpf/bpf-next/c/b4757714cc63
- [bpf-next,v3,2/2] selftests/bpf: Enable arena LDSX tests for riscv64
https://git.kernel.org/bpf/bpf-next/c/8f2087a1b43b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Chen Pei <cp0613@linux.alibaba.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
memxor@gmail.com, bjorn@kernel.org, puranjay@kernel.org,
ihor.solodrai@linux.dev, eddyz87@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, pulehui@huawei.com, pjw@kernel.org,
palmer@dabbelt.com, shuah@kernel.org, guoren@kernel.org,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] bpf, riscv: Add support for signed arena loads
Date: Tue, 25 Aug 2026 13:30:09 +0000 [thread overview]
Message-ID: <178766460914.3460835.2556196507996630304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1787140923.git.cp0613@linux.alibaba.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 19 Aug 2026 20:09:22 +0800 you wrote:
> Hi,
>
> Signed loads from arena memory are currently unsupported on riscv64:
> bpf_jit_supports_insn() rejects BPF_MEMSX loads when in_arena is set,
> so the verifier fails such programs with "sign extending loads from
> arena are not supported yet". The x86 and arm64 JITs gained support
> for them in v6.18 (a91ae3c89311, eab2a71f3a6a). Since compilers are
> free to generate signed loads into arena memory (e.g. GCC-14 was
> reported to do so), otherwise valid BPF programs fail to load on
> riscv64.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf, riscv: Add support for signed arena loads
https://git.kernel.org/bpf/bpf-next/c/b4757714cc63
- [bpf-next,v3,2/2] selftests/bpf: Enable arena LDSX tests for riscv64
https://git.kernel.org/bpf/bpf-next/c/8f2087a1b43b
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
next prev parent reply other threads:[~2026-08-25 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 12:09 [PATCH bpf-next v3 0/2] bpf, riscv: Add support for signed arena loads Chen Pei
2026-08-19 12:09 ` Chen Pei
2026-08-19 12:09 ` [PATCH bpf-next v3 1/2] " Chen Pei
2026-08-19 12:09 ` Chen Pei
2026-08-20 4:12 ` Pu Lehui
2026-08-20 4:12 ` Pu Lehui
2026-08-19 12:09 ` [PATCH bpf-next v3 2/2] selftests/bpf: Enable arena LDSX tests for riscv64 Chen Pei
2026-08-19 12:09 ` Chen Pei
2026-08-20 4:12 ` Pu Lehui
2026-08-20 4:12 ` Pu Lehui
2026-08-25 13:16 ` [PATCH bpf-next v3 0/2] bpf, riscv: Add support for signed arena loads Björn Töpel
2026-08-25 13:16 ` Björn Töpel
2026-08-25 13:30 ` patchwork-bot+netdevbpf [this message]
2026-08-25 13: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=178766460914.3460835.2556196507996630304.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cp0613@linux.alibaba.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=guoren@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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=puranjay@kernel.org \
--cc=shuah@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.