From: Varun R Mallya <varunrmallya@gmail.com>
To: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, bjorn@kernel.org,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
puranjay@kernel.org, menglong8.dong@gmail.com
Cc: martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, pulehui@huawei.com, alex@ghiti.fr,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
varunrmallya@gmail.com
Subject: [PATCH bpf-next 0/2] RISC-V JIT support for bpf_get_current_task/_btf
Date: Wed, 3 Jun 2026 02:28:45 +0530 [thread overview]
Message-ID: <20260602205847.102825-1-varunrmallya@gmail.com> (raw)
These two patches add support for the bpf_get_current_task and
bpf_get_current_task_btf kfuncs in RISC-V JIT and add a selftest.
The first patch adds support for cpu and feature detection on
the JIT disassembly helper function as RISC-V JITed code was not
being disassembled using `LLVMCreateDisasm` as it was missing the
"+c" CPU feature and JITed code contained RISC-V Compressed (C)
Extension. This patch generalizes that to detect CPU features and
enables testing on more RISC-V JIT work ahead.
The second patch, which actually adds this support has been benchmarked
on QEMU RISC-V and shows significant improvements.
It was benchmarked using a simple loop inside a bpf program that ran
bpf_get_current_task() and execution time was measured. It used
bpf_prog_test_run_opts() to repeatedly trigger the BPF program. The loop
ran in 1 second intervals and it kept firing bpf_prog_test_run_opts() as
fast as possible until a second had elapsed and then reported statistics.
Varun R Mallya (2):
selftests/bpf: use host CPU features in JIT disassembler
bpf, riscv: inline bpf_get_current_task() and
bpf_get_current_task_btf()
arch/riscv/net/bpf_jit_comp64.c | 9 +++++++++
tools/testing/selftests/bpf/jit_disasm_helpers.c | 13 +++++++++++--
.../selftests/bpf/progs/verifier_jit_inline.c | 2 ++
3 files changed, 22 insertions(+), 2 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-02 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 20:58 Varun R Mallya [this message]
2026-06-02 20:58 ` [PATCH bpf-next 1/2] selftests/bpf: use host CPU features in JIT disassembler Varun R Mallya
2026-06-03 7:21 ` Björn Töpel
2026-06-02 20:58 ` [PATCH bpf-next 2/2] bpf, riscv: inline bpf_get_current_task() and bpf_get_current_task_btf() Varun R Mallya
2026-06-03 7:16 ` Björn Töpel
2026-06-05 22:30 ` [PATCH bpf-next 0/2] RISC-V JIT support for bpf_get_current_task/_btf 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=20260602205847.102825-1-varunrmallya@gmail.com \
--to=varunrmallya@gmail.com \
--cc=alex@ghiti.fr \
--cc=andrii@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--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=menglong8.dong@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.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 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®