From: Tianyi Chen <diannaaav@gmail.com>
To: qmo@kernel.org, bpf@vger.kernel.org
Cc: andrii@kernel.org, eddyz87@gmail.com, ihor.solodrai@linux.dev,
linux-kselftest@vger.kernel.org
Subject: [PATCH bpf-next v3 0/2] bpftool: Consume ring buffer maps with event_pipe
Date: Fri, 11 Sep 2026 10:51:12 +0800 [thread overview]
Message-ID: <20260911025114.190899-1-diannaaav@gmail.com> (raw)
Extend map event_pipe to BPF ring buffer maps using libbpf's ring buffer
manager. Print complete records in plain or JSON format, reject CPU/index
selectors for ring buffers, and document the shared consumer position.
Changes in v3:
- Remove redundant wording from the manual while retaining the warning
about consuming records and sharing the consumer position.
- Explain callback stopping and signal handling in the commit message.
- Rebase onto current bpf-next and use Assisted-by: LLM.
The implementation and v2 tests, including pretty output, pinned paths,
empty streams and the perf-event-array regression case, are unchanged.
v2: https://lore.kernel.org/r/178874362960.1415955.14971768495630842802.ringbuf-v2-0@tychen.cc
Request: https://github.com/libbpf/bpftool/issues/54
The previous version's CI PR expired after repeated "Patch is empty"
reports. The revised series applies cleanly to the current tree and is
sent as a new thread using git format-patch and git send-email.
Validation:
- Built bpftool and its manual pages, and built the focused selftest
runner with LLVM 20.
- All 17 bpftool_ringbuf subtests passed with no skips or failures
in an x86-64 KVM guest running Linux 7.3.0-rc2 from current bpf/master.
- The four bpftool series were tested together: all 69 subtests passed.
The cpumask suite (36 subtests) and test_maps also passed with no skips.
- Bash syntax and the existing bpftool synchronization checks passed.
This was a focused run; unrelated selftests requiring unavailable kernel
features were excluded from the build with PERMISSIVE=1.
Tianyi Chen (2):
bpftool: Read ring buffer maps with event_pipe
selftests/bpf: Cover bpftool ring buffer event_pipe
.../bpf/bpftool/Documentation/bpftool-map.rst | 14 +-
tools/bpf/bpftool/bash-completion/bpftool | 4 +-
tools/bpf/bpftool/map_perf_ring.c | 87 +++-
.../bpf/prog_tests/bpftool_ringbuf.c | 425 ++++++++++++++++++
.../selftests/bpf/progs/bpftool_ringbuf.c | 47 ++
5 files changed, 553 insertions(+), 24 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/bpftool_ringbuf.c
create mode 100644 tools/testing/selftests/bpf/progs/bpftool_ringbuf.c
base-commit: af0b84a9215d951d16f26b7ee34353b970cf5d4e
--
2.55.0
next reply other threads:[~2026-09-11 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 2:51 Tianyi Chen [this message]
2026-09-11 2:51 ` [PATCH bpf-next v3 1/2] bpftool: Read ring buffer maps with event_pipe Tianyi Chen
2026-09-11 2:51 ` [PATCH bpf-next v3 2/2] selftests/bpf: Cover bpftool ring buffer event_pipe Tianyi Chen
2026-09-11 3:57 ` bot+bpf-ci
[not found] ` <e7211adda619bf43e17dbaf59ffec76ca2442726a5e22485cd783ed9a5e9c655@mail.kernel.org>
2026-09-11 5:12 ` [PATCH bpf-next v3 0/2] bpftool: Consume ring buffer maps with event_pipe Tianyi Chen
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=20260911025114.190899-1-diannaaav@gmail.com \
--to=diannaaav@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kselftest@vger.kernel.org \
--cc=qmo@kernel.org \
/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