Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <[email protected]>:

On Fri,  9 Oct 2026 12:23:17 +0100 you wrote:
> If CONFIG_DEBUG_INFO_BTF_INLINE=y|m, add the "inline" BTF feature
> and encode inline site info in BTF alongside standard BTF data.
> resolve_btfids will then partition into non- and inline-related
> info and split BTF will be used to store inline info in a
> .BTF.inline section in vmlinux and modules.  For
> CONFIG_DEBUG_INFO_BTF=m, vmlinux inline info will be stored
> in btf_vmlinux_inline.ko and will be loaded on-demand if used
> via /sys/kernel/btf/vmlinux.inline.  A .BTF.inline.link section
> in vmlinux stores the module name, the SHA of the BTF and the
> size so that even without loading the kernel can size the
> sysfs representation correctly.  This approach is based on [1]
> and the .BTF.inline.link section is modeled on .GNU_debuglink.
> 
> [...]

Here is the summary with links:
  - [v4,bpf-next,1/7] resolve_btfids: Build separate main and inline BTF objects
    https://git.kernel.org/bpf/bpf-next/c/cf91a7db92c6
  - [v4,bpf-next,2/7] resolve_btfids: Populate BTF link section
    https://git.kernel.org/bpf/bpf-next/c/aac67645215d
  - [v4,bpf-next,3/7] kbuild, btf: Expose vmlinux inline BTF through sysfs
    https://git.kernel.org/bpf/bpf-next/c/672981f4aec1
  - [v4,bpf-next,4/7] btf: Preserve string relocation maps for split BTF
    https://git.kernel.org/bpf/bpf-next/c/5876080366ae
  - [v4,bpf-next,5/7] btf: Relocate and expose module inline BTF
    https://git.kernel.org/bpf/bpf-next/c/42d7153fcb44
  - [v4,bpf-next,6/7] selftests/bpf: Test BTF sysfs inline representations
    https://git.kernel.org/bpf/bpf-next/c/d0de4dc51247
  - [v4,bpf-next,7/7] selftests/bpf: Add a test verifying inline information
    https://git.kernel.org/bpf/bpf-next/c/400f0881c912

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



Reply via email to