From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
qmo@kernel.org, jolsa@kernel.org, daniel@iogearbox.net,
ihor.solodrai@linux.dev, yonghong.song@linux.dev,
song@kernel.org, martin.lau@linux.dev, memxor@gmail.com,
emil@etsalapatis.com, bpf@vger.kernel.org, nsc@kernel.org,
puranjay@kernel.org, yatsenko@meta.com
Subject: Re: [PATCH v4 bpf-next 00/11] Support inline functions in BTF
Date: Thu, 24 Sep 2026 16:10:08 +0000 [thread overview]
Message-ID: <179026620815.1631477.1701211223849452726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260924111428.75957-1-alan.maguire@oracle.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 24 Sep 2026 12:14:17 +0100 you wrote:
> This series adds support to facilitate tracing of inline function
> sites using BPF Type Format (BTF) information. An excellent overview
> of the problem and proposed solution presented at LSF/MM/BPF is
> available at [1].
>
> The aim is to produce a compact representation providing sufficient
> information to a tracer wishing to instrument an inline site via a
> kprobe. The challenge to solve is compact representation - my
> local bpf-next builds show nearly 600,000 inline sites for approximately
> 100,000 functions. Any BTF representation should utilize deduplication
> where possible to minimize overheads.
>
> [...]
Here is the summary with links:
- [v4,bpf-next,01/11] btf: Extend UAPI to support BTF location (inline site) info
https://git.kernel.org/bpf/bpf-next/c/33c5a3278bdb
- [v4,bpf-next,02/11] libbpf: Add support for BTF kinds LOC[_PARAM|_PROTO|SEC]
https://git.kernel.org/bpf/bpf-next/c/dad2fcc644dd
- [v4,bpf-next,03/11] selftests/bpf: Test helper support for BTF_KIND_LOC[_PARAM|_PROTO|SEC]
https://git.kernel.org/bpf/bpf-next/c/0f1de9408e59
- [v4,bpf-next,04/11] selftests/bpf: Add LOC_PARAM, LOC_PROTO, LOCSEC to field iter tests
https://git.kernel.org/bpf/bpf-next/c/663fa771389d
- [v4,bpf-next,05/11] selftests/bpf: Add LOC_PARAM, LOC_PROTO, LOCSEC to dedup split tests
https://git.kernel.org/bpf/bpf-next/c/dfb463b07117
- [v4,bpf-next,06/11] selftests/bpf: BTF distill tests to ensure LOC[_PARAM|_PROTO] add to split BTF
https://git.kernel.org/bpf/bpf-next/c/49a4c23a2234
- [v4,bpf-next,07/11] bpftool: Handle multi-split BTF by supporting multiple base BTFs
https://git.kernel.org/bpf/bpf-next/c/7890a57356a2
- [v4,bpf-next,08/11] bpftool: Document support for multi-split BTF
https://git.kernel.org/bpf/bpf-next/c/0ec4caf73ce5
- [v4,bpf-next,09/11] bpftool: Add ability to dump LOC_PARAM, LOC_PROTO and LOCSEC
https://git.kernel.org/bpf/bpf-next/c/321562c34d5b
- [v4,bpf-next,10/11] selftests/bpf: Test bpftool dump of BTF location info
https://git.kernel.org/bpf/bpf-next/c/3429e01578b6
- [v4,bpf-next,11/11] Documentation/bpf: Describe new location-related BTF kinds
https://git.kernel.org/bpf/bpf-next/c/ce2913d959a2
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:[~2026-09-24 16:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 11:14 [PATCH v4 bpf-next 00/11] Support inline functions in BTF Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 01/11] btf: Extend UAPI to support BTF location (inline site) info Alan Maguire
2026-09-24 12:12 ` bot+bpf-ci
2026-09-24 15:18 ` Alexei Starovoitov
2026-09-24 11:14 ` [PATCH v4 bpf-next 02/11] libbpf: Add support for BTF kinds LOC[_PARAM|_PROTO|SEC] Alan Maguire
2026-09-24 12:12 ` bot+bpf-ci
2026-09-24 11:14 ` [PATCH v4 bpf-next 03/11] selftests/bpf: Test helper support for BTF_KIND_LOC[_PARAM|_PROTO|SEC] Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 04/11] selftests/bpf: Add LOC_PARAM, LOC_PROTO, LOCSEC to field iter tests Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 05/11] selftests/bpf: Add LOC_PARAM, LOC_PROTO, LOCSEC to dedup split tests Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 06/11] selftests/bpf: BTF distill tests to ensure LOC[_PARAM|_PROTO] add to split BTF Alan Maguire
2026-09-24 11:56 ` bot+bpf-ci
2026-09-24 11:14 ` [PATCH v4 bpf-next 07/11] bpftool: Handle multi-split BTF by supporting multiple base BTFs Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 08/11] bpftool: Document support for multi-split BTF Alan Maguire
2026-09-24 11:14 ` [PATCH v4 bpf-next 09/11] bpftool: Add ability to dump LOC_PARAM, LOC_PROTO and LOCSEC Alan Maguire
2026-09-24 15:16 ` Alexei Starovoitov
2026-09-24 15:33 ` Alan Maguire
2026-09-24 16:02 ` Alexei Starovoitov
2026-09-24 11:14 ` [PATCH v4 bpf-next 10/11] selftests/bpf: Test bpftool dump of BTF location info Alan Maguire
2026-09-24 11:56 ` bot+bpf-ci
2026-09-24 11:14 ` [PATCH v4 bpf-next 11/11] Documentation/bpf: Describe new location-related BTF kinds Alan Maguire
2026-09-24 11:56 ` bot+bpf-ci
2026-09-24 12:19 ` sashiko-bot
2026-09-24 16:10 ` 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=179026620815.1631477.1701211223849452726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@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=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nsc@kernel.org \
--cc=puranjay@kernel.org \
--cc=qmo@kernel.org \
--cc=song@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