From: "Daniel T. Lee" <danieltimlee@gmail.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware
Date: Fri, 18 Aug 2023 18:01:10 +0900 [thread overview]
Message-ID: <20230818090119.477441-1-danieltimlee@gmail.com> (raw)
The existing tracing programs have been developed for a considerable
period of time and, as a result, do not properly incorporate the
features of the current libbpf, such as CO-RE. This is evident in
frequent usage of functions like PT_REGS* and the persistence of "hack"
methods using underscore-style bpf_probe_read_kernel from the past.
These programs are far behind the current level of libbpf and can
potentially confuse users.
The kernel has undergone significant changes, and some of these changes
have broken these programs, but on the other hand, more robust APIs have
been developed for increased stableness.
To list some of the kernel changes that this patch set is focusing on,
- symbol mismatch occurs due to compiler optimization [1]
- inline of blk_account_io* breaks BPF kprobe program [2]
- new tracepoints for the block_io_start/done are introduced [3]
- map lookup probes can't be triggered (bpf_disable_instrumentation)[4]
- BPF_KSYSCALL has been introduced to simplify argument fetching [5]
- convert to vmlinux.h and use tp argument structure within it
- make tracing programs to be more CO-RE centric
In this regard, this patch set aims not only to integrate the latest
features of libbpf into BPF programs but also to reduce confusion and
clarify the BPF programs. This will help with the potential confusion
among users and make the programs more intutitive.
[1]: https://github.com/iovisor/bcc/issues/1754
[2]: https://github.com/iovisor/bcc/issues/4261
[3]: commit 5a80bd075f3b ("block: introduce block_io_start/block_io_done tracepoints")
[4]: commit 7c4cd051add3 ("bpf: Fix syscall's stackmap lookup potential deadlock")
[5]: commit 6f5d467d55f0 ("libbpf: improve BPF_KPROBE_SYSCALL macro and rename it to BPF_KSYSCALL")
Daniel T. Lee (9):
samples/bpf: fix warning with ignored-attributes
samples/bpf: convert to vmlinux.h with tracing programs
samples/bpf: unify bpf program suffix to .bpf with tracing programs
samples/bpf: fix symbol mismatch by compiler optimization
samples/bpf: make tracing programs to be more CO-RE centric
samples/bpf: fix bio latency check with tracepoint
samples/bpf: fix broken map lookup probe
samples/bpf: refactor syscall tracing programs using BPF_KSYSCALL
macro
samples/bpf: simplify spintest with kprobe.multi
samples/bpf/Makefile | 20 +++++-----
samples/bpf/net_shared.h | 2 +
.../{offwaketime_kern.c => offwaketime.bpf.c} | 39 +++++-------------
samples/bpf/offwaketime_user.c | 2 +-
.../bpf/{spintest_kern.c => spintest.bpf.c} | 27 +++++--------
samples/bpf/spintest_user.c | 24 ++++-------
samples/bpf/test_map_in_map.bpf.c | 10 ++---
samples/bpf/test_overhead_kprobe.bpf.c | 20 ++++------
samples/bpf/test_overhead_tp.bpf.c | 29 +-------------
samples/bpf/{tracex1_kern.c => tracex1.bpf.c} | 25 +++++-------
samples/bpf/tracex1_user.c | 2 +-
samples/bpf/{tracex3_kern.c => tracex3.bpf.c} | 40 ++++++++++++-------
samples/bpf/tracex3_user.c | 2 +-
samples/bpf/{tracex4_kern.c => tracex4.bpf.c} | 3 +-
samples/bpf/tracex4_user.c | 2 +-
samples/bpf/{tracex5_kern.c => tracex5.bpf.c} | 12 +++---
samples/bpf/tracex5_user.c | 2 +-
samples/bpf/{tracex6_kern.c => tracex6.bpf.c} | 20 ++++++++--
samples/bpf/tracex6_user.c | 2 +-
samples/bpf/{tracex7_kern.c => tracex7.bpf.c} | 3 +-
samples/bpf/tracex7_user.c | 2 +-
21 files changed, 117 insertions(+), 171 deletions(-)
rename samples/bpf/{offwaketime_kern.c => offwaketime.bpf.c} (76%)
rename samples/bpf/{spintest_kern.c => spintest.bpf.c} (67%)
rename samples/bpf/{tracex1_kern.c => tracex1.bpf.c} (60%)
rename samples/bpf/{tracex3_kern.c => tracex3.bpf.c} (70%)
rename samples/bpf/{tracex4_kern.c => tracex4.bpf.c} (95%)
rename samples/bpf/{tracex5_kern.c => tracex5.bpf.c} (90%)
rename samples/bpf/{tracex6_kern.c => tracex6.bpf.c} (71%)
rename samples/bpf/{tracex7_kern.c => tracex7.bpf.c} (82%)
--
2.34.1
next reply other threads:[~2023-08-18 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:01 Daniel T. Lee [this message]
2023-08-18 9:01 ` [bpf-next 1/9] samples/bpf: fix warning with ignored-attributes Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 2/9] samples/bpf: convert to vmlinux.h with tracing programs Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 3/9] samples/bpf: unify bpf program suffix to .bpf " Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 4/9] samples/bpf: fix symbol mismatch by compiler optimization Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 5/9] samples/bpf: make tracing programs to be more CO-RE centric Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 6/9] samples/bpf: fix bio latency check with tracepoint Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 7/9] samples/bpf: fix broken map lookup probe Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 8/9] samples/bpf: refactor syscall tracing programs using BPF_KSYSCALL macro Daniel T. Lee
2023-08-18 9:01 ` [bpf-next 9/9] samples/bpf: simplify spintest with kprobe.multi Daniel T. Lee
2023-08-21 22:50 ` [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware 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=20230818090119.477441-1-danieltimlee@gmail.com \
--to=danieltimlee@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=johannes.thumshirn@wdc.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--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;
as well as URLs for NNTP newsgroup(s).