From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: support opting out from autoloading BPF programs declaratively
Date: Tue, 19 Apr 2022 21:00:12 +0000 [thread overview]
Message-ID: <165040201224.664.18250423075695493920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220419002452.632125-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 18 Apr 2022 17:24:50 -0700 you wrote:
> Establish SEC("?abc") naming convention (i.e., adding question mark in
> front of otherwise normal section name) that allows to set corresponding
> program's autoload property to false. This is effectively just
> a declarative way to do bpf_program__set_autoload(prog, false).
>
> Having a way to do this declaratively in BPF code itself is useful and
> convenient for various scenarios. E.g., for testing, when BPF object
> consists of multiple independent BPF programs that each needs to be
> tested separately. Opting out all of them by default and then setting
> autoload to true for just one of them at a time simplifies testing code
> (see next patch for few conversions in BPF selftests taking advantage of
> this new feature).
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] libbpf: support opting out from autoloading BPF programs declaratively
https://git.kernel.org/bpf/bpf-next/c/a3820c481112
- [bpf-next,2/2] selftests/bpf: use non-autoloaded programs in few tests
https://git.kernel.org/bpf/bpf-next/c/0d7fefebea55
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:[~2022-04-19 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 0:24 [PATCH bpf-next 1/2] libbpf: support opting out from autoloading BPF programs declaratively Andrii Nakryiko
2022-04-19 0:24 ` [PATCH bpf-next 2/2] selftests/bpf: use non-autoloaded programs in few tests Andrii Nakryiko
2022-04-19 21:00 ` 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=165040201224.664.18250423075695493920.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=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