From: Pu Lehui <pulehui@huawei.com>
To: Chen Pei <cp0613@linux.alibaba.com>, <ast@kernel.org>,
<daniel@iogearbox.net>, <andrii@kernel.org>, <memxor@gmail.com>,
<bjorn@kernel.org>, <puranjay@kernel.org>
Cc: <eddyz87@gmail.com>, <martin.lau@linux.dev>, <song@kernel.org>,
<yonghong.song@linux.dev>, <jolsa@kernel.org>,
<emil@etsalapatis.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 0/2] bpf, riscv: Add support for signed arena loads
Date: Tue, 18 Aug 2026 22:28:28 +0800 [thread overview]
Message-ID: <40134c09-58cf-42c4-b79e-1a461c013a50@huawei.com> (raw)
In-Reply-To: <cover.1786708960.git.cp0613@linux.alibaba.com>
On 2026/8/17 15:24, Chen Pei 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.
>
> This series adds BPF_PROBE_MEM32SX support to the RV64 JIT and
> enables the corresponding selftests on riscv64:
>
> 1 implements signed arena loads in the RV64 JIT. The verifier
> already converts MEMSX loads from PTR_TO_ARENA to
> BPF_PROBE_MEM32SX once bpf_jit_supports_insn() allows them, so
> the JIT reuses the existing arena handling: the arena base
> (RV_REG_ARENA) is added to the source register and the load is
> emitted with sign extension (lb/lh/lw). BPF_PROBE_MEM32SX is also
> added to the add_exception_handler() mode gate so faulting loads
> register an exception table entry that clears the destination
> register and resumes execution.
>
> 2 enables the arena LDSX tests on riscv64: JIT disassembly
> assertions are added to arena_ldsx_disasm, and
> arena_ldsx_exception/s8/s16/s32 are now run on riscv64.
>
> The series was verified on riscv64 with QEMU (-M virt -cpu max): all
> five arena_ldsx tests pass, including the exception path (load from
> unallocated arena memory returns 0) and the sign-extension values
> (s8/s16/s32 tests return -1 as expected).
>
> Note: the __jited assertions in patch 2 were derived from the JIT
> register allocation (R0->a5, R1->a0, R8->s3, R9->s4, arena base in
> s7) and the emit_ldx() code paths; happy to adjust them if a
> disassembler output detail differs.
Test meets happy.
For this series:
Tested-by: Pu Lehui <pulehui@huawei.com>
>
> Thanks,
> Pei
>
> Chen Pei (2):
> bpf, riscv: Add support for signed arena loads
> selftests/bpf: Enable arena LDSX tests for riscv64
>
> arch/riscv/net/bpf_jit_comp64.c | 15 +++++++++------
> .../testing/selftests/bpf/progs/verifier_ldsx.c | 17 +++++++++++++++++
> 2 files changed, 26 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2026-08-18 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 7:24 Chen Pei
2026-08-17 7:24 ` [PATCH bpf-next 1/2] " Chen Pei
2026-08-17 8:16 ` bot+bpf-ci
2026-08-18 14:27 ` Pu Lehui
2026-08-19 3:41 ` Pu Lehui
2026-08-19 8:23 ` Chen Pei
2026-08-17 7:24 ` [PATCH bpf-next 2/2] selftests/bpf: Enable arena LDSX tests for riscv64 Chen Pei
2026-08-18 14:27 ` Pu Lehui
2026-08-18 14:28 ` Pu Lehui [this message]
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=40134c09-58cf-42c4-b79e-1a461c013a50@huawei.com \
--to=pulehui@huawei.com \
--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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®