From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v3 bpf-next 0/9] Libbpf-side __arg_ctx fallback support
Date: Thu, 04 Jan 2024 08:13:02 +0000 [thread overview]
Message-ID: <170435598257.4004.10969640471288058081.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240104013847.3875810-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 3 Jan 2024 17:38:38 -0800 you wrote:
> Support __arg_ctx global function argument tag semantics even on older kernels
> that don't natively support it through btf_decl_tag("arg:ctx").
>
> Patches #2-#6 are preparatory work to allow to postpone BTF loading into the
> kernel until after all the BPF program relocations (including global func
> appending to main programs) are done. Patch #4 is perhaps the most important
> and establishes pre-created stable placeholder FDs, so that relocations can
> embed valid map FDs into ldimm64 instructions.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,1/9] libbpf: make uniform use of btf__fd() accessor inside libbpf
https://git.kernel.org/bpf/bpf-next/c/df7c3f7d3a3d
- [v3,bpf-next,2/9] libbpf: use explicit map reuse flag to skip map creation steps
https://git.kernel.org/bpf/bpf-next/c/fa98b54bff39
- [v3,bpf-next,3/9] libbpf: don't rely on map->fd as an indicator of map being created
https://git.kernel.org/bpf/bpf-next/c/f08c18e083ad
- [v3,bpf-next,4/9] libbpf: use stable map placeholder FDs
https://git.kernel.org/bpf/bpf-next/c/dac645b950ea
- [v3,bpf-next,5/9] libbpf: move exception callbacks assignment logic into relocation step
https://git.kernel.org/bpf/bpf-next/c/fb03be7c4a27
- [v3,bpf-next,6/9] libbpf: move BTF loading step after relocation step
https://git.kernel.org/bpf/bpf-next/c/1004742d7ff0
- [v3,bpf-next,7/9] libbpf: implement __arg_ctx fallback logic
https://git.kernel.org/bpf/bpf-next/c/2f38fe689470
- [v3,bpf-next,8/9] selftests/bpf: add arg:ctx cases to test_global_funcs tests
https://git.kernel.org/bpf/bpf-next/c/67fe459144dd
- [v3,bpf-next,9/9] selftests/bpf: add __arg_ctx BTF rewrite test
https://git.kernel.org/bpf/bpf-next/c/95226f5a3669
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:[~2024-01-04 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 1:38 [PATCH v3 bpf-next 0/9] Libbpf-side __arg_ctx fallback support Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 1/9] libbpf: make uniform use of btf__fd() accessor inside libbpf Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 2/9] libbpf: use explicit map reuse flag to skip map creation steps Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 3/9] libbpf: don't rely on map->fd as an indicator of map being created Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 4/9] libbpf: use stable map placeholder FDs Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 5/9] libbpf: move exception callbacks assignment logic into relocation step Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 6/9] libbpf: move BTF loading step after " Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 7/9] libbpf: implement __arg_ctx fallback logic Andrii Nakryiko
2024-01-04 5:39 ` Alexei Starovoitov
2024-01-04 18:37 ` Andrii Nakryiko
2024-01-04 18:52 ` Alexei Starovoitov
2024-01-04 20:58 ` Andrii Nakryiko
2024-01-05 1:33 ` Alexei Starovoitov
2024-01-05 3:57 ` Andrii Nakryiko
2024-01-05 5:42 ` Alexei Starovoitov
2024-01-08 23:45 ` Andrii Nakryiko
2024-01-09 1:49 ` Alexei Starovoitov
2024-01-09 17:17 ` Andrii Nakryiko
2024-01-10 1:58 ` Alexei Starovoitov
2024-01-10 19:02 ` Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 8/9] selftests/bpf: add arg:ctx cases to test_global_funcs tests Andrii Nakryiko
2024-01-04 1:38 ` [PATCH v3 bpf-next 9/9] selftests/bpf: add __arg_ctx BTF rewrite test Andrii Nakryiko
2024-01-04 2:33 ` [PATCH v3 bpf-next 0/9] Libbpf-side __arg_ctx fallback support Eduard Zingerman
2024-01-04 8:13 ` 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=170435598257.4004.10969640471288058081.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@meta.com \
--cc=martin.lau@kernel.org \
/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