BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, jolsa@kernel.org, ihor.solodrai@linux.dev,
	yonghong.song@linux.dev, song@kernel.org, qmo@kernel.org,
	martin.lau@linux.dev, memxor@gmail.com, emil@etsalapatis.com,
	mcgrof@kernel.org, petr.pavlu@suse.com, tj@kernel.org,
	kees@kernel.org, nathan@kernel.org, arnd@arndb.de,
	puranjay@kernel.org, yatsenko@meta.com, atenart@kernel.org,
	ojeda@kernel.org, linux-modules@vger.kernel.org,
	arnaldo.melo@gmail.com, bpf@vger.kernel.org
Subject: Re: [PATCH v4 bpf-next 0/7] kbuild, bpf: Support inline info in BTF
Date: Sun, 11 Oct 2026 14:40:13 +0000	[thread overview]
Message-ID: <179172961326.2072230.906820075160340410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261009112324.1442319-1-alan.maguire@oracle.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

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



      parent reply	other threads:[~2026-10-11 14:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 11:23 [PATCH v4 bpf-next 0/7] kbuild, bpf: Support inline info in BTF Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 1/7] resolve_btfids: Build separate main and inline BTF objects Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 2/7] resolve_btfids: Populate BTF link section Alan Maguire
2026-10-09 12:24   ` bot+bpf-ci
2026-10-09 11:23 ` [PATCH v4 bpf-next 3/7] kbuild, btf: Expose vmlinux inline BTF through sysfs Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 4/7] btf: Preserve string relocation maps for split BTF Alan Maguire
2026-10-09 12:01   ` sashiko-bot
2026-10-09 14:00     ` Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 5/7] btf: Relocate and expose module inline BTF Alan Maguire
2026-10-09 11:23 ` [PATCH v4 bpf-next 6/7] selftests/bpf: Test BTF sysfs inline representations Alan Maguire
2026-10-09 12:25   ` sashiko-bot
2026-10-11 14:29   ` Alexei Starovoitov
2026-10-09 11:23 ` [PATCH v4 bpf-next 7/7] selftests/bpf: Add a test verifying inline information Alan Maguire
2026-10-09 12:33   ` sashiko-bot
2026-10-11 14:40 ` 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=179172961326.2072230.906820075160340410.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=arnd@arndb.de \
    --cc=ast@kernel.org \
    --cc=atenart@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=ihor.solodrai@linux.dev \
    --cc=jolsa@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mcgrof@kernel.org \
    --cc=memxor@gmail.com \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=puranjay@kernel.org \
    --cc=qmo@kernel.org \
    --cc=song@kernel.org \
    --cc=tj@kernel.org \
    --cc=yatsenko@meta.com \
    --cc=yonghong.song@linux.dev \
    /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