From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com, yatsenko@meta.com
Subject: Re: [PATCH bpf-next v2 0/4] Introduce bpf_object__prepare
Date: Mon, 03 Mar 2025 23:36:05 +0000 [thread overview]
Message-ID: <174104496548.3745415.10380206773751586157.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303135752.158343-1-mykyta.yatsenko5@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 3 Mar 2025 13:57:48 +0000 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> We are introducing a new function in the libbpf API, bpf_object__prepare,
> which provides more granular control over the process of loading a
> bpf_object. bpf_object__prepare performs ELF processing, relocations,
> prepares final state of BPF program instructions (accessible with
> bpf_program__insns()), creates and potentially pins maps, and stops short
> of loading BPF programs.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] libbpf: use map_is_created helper in map setters
https://git.kernel.org/bpf/bpf-next/c/7218ff1f322d
- [bpf-next,v2,2/4] libbpf: introduce more granular state for bpf_object
https://git.kernel.org/bpf/bpf-next/c/8ca8f6d1a2b4
- [bpf-next,v2,3/4] libbpf: split bpf object load into prepare/load
https://git.kernel.org/bpf/bpf-next/c/da755540c6f8
- [bpf-next,v2,4/4] selftests/bpf: add tests for bpf_object__prepare
https://git.kernel.org/bpf/bpf-next/c/68b61a823aab
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-03 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:57 [PATCH bpf-next v2 0/4] Introduce bpf_object__prepare Mykyta Yatsenko
2025-03-03 13:57 ` [PATCH bpf-next v2 1/4] libbpf: use map_is_created helper in map setters Mykyta Yatsenko
2025-03-03 13:57 ` [PATCH bpf-next v2 2/4] libbpf: introduce more granular state for bpf_object Mykyta Yatsenko
2025-03-03 13:57 ` [PATCH bpf-next v2 3/4] libbpf: split bpf object load into prepare/load Mykyta Yatsenko
2025-03-03 23:23 ` Andrii Nakryiko
2025-03-03 13:57 ` [PATCH bpf-next v2 4/4] selftests/bpf: add tests for bpf_object__prepare Mykyta Yatsenko
2025-03-03 23:36 ` patchwork-bot+netdevbpf [this message]
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=174104496548.3745415.10380206773751586157.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=mykyta.yatsenko5@gmail.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