From: Andrii Nakryiko <andrii@kernel.org>
To: <bpf@vger.kernel.org>, <ast@kernel.org>, <daniel@iogearbox.net>
Cc: <andrii@kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/3] Add target-less tracing SEC() definitions
Date: Fri, 8 Apr 2022 13:34:30 -0700 [thread overview]
Message-ID: <20220408203433.2988727-1-andrii@kernel.org> (raw)
Allow specifying "target-less" SEC() definitions for tracing BPF programs,
both non-BTF-backed (kprobes, tracepoints, raw tracepoints) and BTF-backed
(fentry/fexit, iter, lsm, etc).
There are various situations where attach target cannot be known at
compilation time, so libbpf's insistence on specifying something leads to
users having to add random test like SEC("kprobe/whatever") and then
specifying correct target at runtime using APIs like
bpf_program__attach_kprobe().
So this patch set improves ergonomics by allowing simple SEC() definitions
that define BPF program type and nothing else. Such programs won't be
auto-attachable, of course, but they also won't fail skeleton auto-attachment,
just like we do this for uprobes.
Andrii Nakryiko (3):
libbpf: allow "incomplete" basic tracing SEC() definitions
libbpf: support target-less SEC() definitions for BTF-backed programs
selftests/bpf: use target-less SEC() definitions in various tests
tools/lib/bpf/libbpf.c | 118 ++++++++++++------
.../selftests/bpf/prog_tests/attach_probe.c | 10 ++
.../bpf/prog_tests/kprobe_multi_test.c | 14 +--
.../selftests/bpf/progs/kprobe_multi.c | 14 +++
.../selftests/bpf/progs/test_attach_probe.c | 23 +++-
.../selftests/bpf/progs/test_module_attach.c | 2 +-
6 files changed, 135 insertions(+), 46 deletions(-)
--
2.30.2
next reply other threads:[~2022-04-08 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 20:34 Andrii Nakryiko [this message]
2022-04-08 20:34 ` [PATCH bpf-next 1/3] libbpf: allow "incomplete" basic tracing SEC() definitions Andrii Nakryiko
2022-04-08 20:46 ` Song Liu
2022-04-08 22:21 ` Andrii Nakryiko
2022-04-08 22:36 ` Song Liu
2022-04-08 20:34 ` [PATCH bpf-next 2/3] libbpf: support target-less SEC() definitions for BTF-backed programs Andrii Nakryiko
2022-04-08 21:08 ` Song Liu
2022-04-08 20:34 ` [PATCH bpf-next 3/3] selftests/bpf: use target-less SEC() definitions in various tests Andrii Nakryiko
2022-04-08 21:08 ` Song Liu
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=20220408203433.2988727-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.