From: Nick Alcock <nick.alcock@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, elena.zannoni@oracle.com,
bruce.mcculloch@oracle.com, jose.marchesi@oracle.com
Subject: [[LSF/MM/BPF TOPIC] Progress on BTF linking and deduplication using the toolchain
Date: Thu, 19 Feb 2026 19:57:21 +0000 [thread overview]
Message-ID: <87h5rcfqvy.fsf@esperi.org.uk> (raw)
This talk will provide an update on the work we have done in binutils and
pahole to support BTF.
We have been working on pahole modifications, intended for use with
GCC-generated BTF information, providing a more direct handling of BTF
without the need for DWARF to BTF conversion.
This is done using libctf from binutils, which as of our latest version (not
yet on binutils master), can read and write BTF in a way that is fully
compatible with the existing mechanism. We also have added support for
merging and deduplicating BTF in the linker. In addition we can now dump
BTF with objdump.
We will show comparisons between the old and new approach within pahole,
which will exemplify differences in speed, as well as the lack of
differences in output.
This talk will give a brief overview of how this works as well as a short
demonstration.
(Like several others, I'm hoping I can do this remotely: transport from
the UK across Bank Holiday Monday is something between awful and
abominable.
I've added a couple of other possible attendees -- Cc:ed -- to the
Google form side of this: if this was overstepping some sort of bound,
since I'm not a subsystem maintainer of any sort, my apologies.)
next reply other threads:[~2026-02-19 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 19:57 Nick Alcock [this message]
2026-02-20 23:37 ` [[LSF/MM/BPF TOPIC] Progress on BTF linking and deduplication using the toolchain Elena Zannoni
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=87h5rcfqvy.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=bruce.mcculloch@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
/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