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/4] libbpf: Streamline internal BPF program sections handling
Date: Mon, 13 Sep 2021 18:47:29 -0700 [thread overview]
Message-ID: <20210914014733.2768-1-andrii@kernel.org> (raw)
This small patch set performs internal refactorings around libbpf BPF program
ELF section definitions' handling. This is preparatory changes for further
changes around making libbpf BPF program section handling more strict but also
pluggable and customizable, as part of the libbpf 1.0 effort. See individual
patches for details.
Andrii Nakryiko (4):
selftests/bpf: update selftests to always provide "struct_ops" SEC
libbpf: ensure BPF prog types are set before relocations
libbpf: simplify BPF program auto-attach code
libbpf: minimize explicit iterator of section definition array
tools/lib/bpf/libbpf.c | 200 ++++++++----------
tools/testing/selftests/bpf/progs/bpf_cubic.c | 12 +-
2 files changed, 95 insertions(+), 117 deletions(-)
--
2.30.2
next reply other threads:[~2021-09-14 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 1:47 Andrii Nakryiko [this message]
2021-09-14 1:47 ` [PATCH bpf-next 1/4] selftests/bpf: update selftests to always provide "struct_ops" SEC Andrii Nakryiko
2021-09-14 17:21 ` Martin KaFai Lau
2021-09-14 1:47 ` [PATCH bpf-next 2/4] libbpf: ensure BPF prog types are set before relocations Andrii Nakryiko
2021-09-14 17:22 ` Martin KaFai Lau
2021-09-14 1:47 ` [PATCH bpf-next 3/4] libbpf: simplify BPF program auto-attach code Andrii Nakryiko
2021-09-14 17:32 ` Martin KaFai Lau
2021-09-14 1:47 ` [PATCH bpf-next 4/4] libbpf: minimize explicit iterator of section definition array Andrii Nakryiko
2021-09-14 17:32 ` Martin KaFai Lau
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=20210914014733.2768-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 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).