Re: [PATCH v6 bpf-next 0/9] bpf: support resilient split BTF

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Thu, 13 Jun 2024 10:50:05 +0100 you wrote:
> Split BPF Type Format (BTF) provides huge advantages in that kernel
> modules only have to provide type information for types that they do not
> share with the core kernel; for core kernel types, split BTF refers to
> core kernel BTF type ids.  So for a STRUCT sk_buff, a module that
> uses that structure (or a pointer to it) simply needs to refer to the
> core kernel type id, saving the need to define the structure and its many
> dependents.  This cuts down on duplication and makes BTF as compact
> as possible.
> 
> [...]

Here is the summary with links:
  - [v6,bpf-next,1/9] libbpf: add btf__distill_base() creating split BTF with distilled base BTF
    https://git.kernel.org/bpf/bpf-next/c/58e185a0dc35
  - [v6,bpf-next,2/9] selftests/bpf: test distilled base, split BTF generation
    https://git.kernel.org/bpf/bpf-next/c/eb20e727c434
  - [v6,bpf-next,3/9] libbpf: split BTF relocation
    https://git.kernel.org/bpf/bpf-next/c/19e00c897d50
  - [v6,bpf-next,4/9] selftests/bpf: extend distilled BTF tests to cover BTF relocation
    https://git.kernel.org/bpf/bpf-next/c/affdeb50616b
  - [v6,bpf-next,5/9] libbpf: make btf_parse_elf process .BTF.base transparently
    https://git.kernel.org/bpf/bpf-next/c/c86f180ffc99
  - [v6,bpf-next,6/9] resolve_btfids: handle presence of .BTF.base section
    https://git.kernel.org/bpf/bpf-next/c/6ba77385f386
  - [v6,bpf-next,7/9] module, bpf: store BTF base pointer in struct module
    (no matching commit)
  - [v6,bpf-next,8/9] libbpf,bpf: share BTF relocate-related code with kernel
    (no matching commit)
  - [v6,bpf-next,9/9] kbuild,bpf: add module-specific pahole flags for distilled base BTF
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html