From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: [PATCH bpf-next 0/3] Introduce bpf_object__prepare
Date: Fri, 28 Feb 2025 17:52:52 +0000 [thread overview]
Message-ID: <20250228175255.254009-1-mykyta.yatsenko5@gmail.com> (raw)
From: Mykyta Yatsenko <yatsenko@meta.com>
Introduce a new libbpf API function bpf_object__prepare enabling more
granular control over the process of bpf_object loading.
bpf_object__prepare runs the same steps that bpf_object__load is running,
before the actual loading of BPF programs.
This API could be useful when we need access to initialized fields of
bpf_object before program loading, for example: currently we can't pass
bpf_token into bpf_program__set_attach_target, because token initialization
is done during loading.
Mykyta Yatsenko (3):
libbpf: introduce more granular state for bpf_object
libbpf: split bpf object load into prepare/load
selftests/bpf: add tests for bpf_object__prepare
tools/lib/bpf/libbpf.c | 194 ++++++++++++------
tools/lib/bpf/libbpf.h | 9 +
tools/lib/bpf/libbpf.map | 1 +
.../selftests/bpf/prog_tests/prepare.c | 99 +++++++++
tools/testing/selftests/bpf/progs/prepare.c | 28 +++
5 files changed, 267 insertions(+), 64 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/prepare.c
create mode 100644 tools/testing/selftests/bpf/progs/prepare.c
--
2.48.1
next reply other threads:[~2025-02-28 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 17:52 Mykyta Yatsenko [this message]
2025-02-28 17:52 ` [PATCH bpf-next 1/3] libbpf: introduce more granular state for bpf_object Mykyta Yatsenko
2025-02-28 22:20 ` Andrii Nakryiko
2025-02-28 22:35 ` Andrii Nakryiko
2025-02-28 17:52 ` [PATCH bpf-next 2/3] libbpf: split bpf object load into prepare/load Mykyta Yatsenko
2025-02-28 22:31 ` Andrii Nakryiko
2025-03-01 8:12 ` Eduard Zingerman
2025-03-01 21:45 ` Mykyta Yatsenko
2025-03-03 21:38 ` Andrii Nakryiko
2025-03-03 22:04 ` Eduard Zingerman
2025-03-03 23:27 ` Andrii Nakryiko
2025-02-28 17:52 ` [PATCH bpf-next 3/3] selftests/bpf: add tests for bpf_object__prepare Mykyta Yatsenko
2025-02-28 22:39 ` [PATCH bpf-next 0/3] Introduce bpf_object__prepare Andrii Nakryiko
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=20250228175255.254009-1-mykyta.yatsenko5@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=yatsenko@meta.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