From: Jiri Olsa <olsajiri@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
qmo@kernel.org, ihor.solodrai@linux.dev,
mykyta.yatsenko5@gmail.com, dwarves@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH v3 dwarves 0/2] pahole: add BTF layout encoding feature
Date: Fri, 3 Apr 2026 23:08:35 +0200 [thread overview]
Message-ID: <adAsUx82TbLx4PfS@krava> (raw)
In-Reply-To: <20260226085240.1908874-1-alan.maguire@oracle.com>
On Thu, Feb 26, 2026 at 08:52:38AM +0000, Alan Maguire wrote:
> A soon-to-arrive v9 series will add support to add BTF layout
> information to BTF; this describes the BTF kinds known about at
> time of encoding in order to support parsing even in cases where
> the kinds are not known to the parser; the layout relates a
> BTF kind to the amount of space it consumes via an optional single
> element following the BTF type or a set of vlen-specified objects.
>
> This series implements the support for the BTF "layout" feature
> but does not require the libbpf changes to support it; the feature
> test uses a weak declaration of btf__new_empty_opts() to handle the
> unsupported case.
>
> To test pahole with this feature, the following approach can be used;
>
> 1. Specify -DLIBBPF_EMBEDDED=OFF option to cmake
> 2. Install latest libbpf with associated patch series with layout support
>
> Alternatively with embedded libbpf the changes can be applied to
> the embedded libbpf in lib/bpf/src.
>
> Changes since v2 [1]:
>
> - Resynced, renamed kind_layout -> layout
> - Avoid encoding layout info in split BTF since it is a waste of space
>
> Changes since v1 [2]:
>
> - Resynced with latest pahole
>
> [1] https://lore.kernel.org/dwarves/20251210202752.813919-1-alan.maguire@oracle.com/
> [2] https://lore.kernel.org/dwarves/20250528095349.788793-1-alan.maguire@oracle.com/
>
> Alan Maguire (2):
> pahole: Add "layout" BTF encoding feature
> man-pages: describe layout BTF feature
lgtm
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
>
> btf_encoder.c | 21 ++++++++++++++++++++-
> dwarves.h | 4 ++++
> man-pages/pahole.1 | 2 ++
> pahole.c | 6 ++++++
> 4 files changed, 32 insertions(+), 1 deletion(-)
>
> --
> 2.39.3
>
prev parent reply other threads:[~2026-04-03 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 8:52 [PATCH v3 dwarves 0/2] pahole: add BTF layout encoding feature Alan Maguire
2026-02-26 8:52 ` [PATCH v3 dwarves 1/2] pahole: Add "layout" BTF " Alan Maguire
2026-02-26 8:52 ` [PATCH v3 dwarves 2/2] man-pages: describe layout BTF feature Alan Maguire
2026-04-02 8:00 ` [PATCH v3 dwarves 0/2] pahole: add BTF layout encoding feature Alan Maguire
2026-04-02 14:03 ` Alexei Starovoitov
2026-04-03 21:08 ` Jiri Olsa [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=adAsUx82TbLx4PfS@krava \
--to=olsajiri@gmail.com \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykyta.yatsenko5@gmail.com \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.