diff options
| author | 2026-06-05 15:26:18 -0700 | |
|---|---|---|
| committer | 2026-06-05 15:26:18 -0700 | |
| commit | b9845290525cf19d29f3a0d06ae3feb923f60e4c (patch) | |
| tree | 10d38a84624b2a60caa3d05cc9f32b41bc18428d /tools/lib/python/kdoc/python_version.py | |
| parent | Merge branch 'bpf-check-tail-zero-of-bpf_map_info-and-bpf_prog_info' (diff) | |
| parent | bpf, riscv: inline bpf_get_current_task() and bpf_get_current_task_btf() (diff) | |
Merge branch 'risc-v-jit-support-for-bpf_get_current_task-_btf'
Varun R Mallya says:
====================
RISC-V JIT support for bpf_get_current_task/_btf
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.
====================
Link: https://patch.msgid.link/20260602205847.102825-1-varunrmallya@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
