From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org, dwarves@vger.kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Alan Maguire <alan.maguire@oracle.com>
Subject: [LSF/MM/BPF TOPIC] pahole + BTF update and next steps
Date: Tue, 14 Jan 2025 13:21:15 -0300 [thread overview]
Message-ID: <Z4aO-4mkXi4ID7xs@x1> (raw)
Hi,
I'd like to propose a BPF activity on a pahole + BTF update,
mentioning features that were implemented since last year, changes in
the release cadence, testing, and maintainance of pahole.
Also about preparing it for when BTF gets natively generated by
gcc/clang for the kernel, when it becomes a BTF "augmenter", adding
extra info or removing/fixing initial compiler BTF generation problems.
This would be kinda complementary to José's "Compiled BPF"
proposal, I guess.
There are also new usage in perf of BPF and BTF that could be
covered, if there's interest in that as well.
Thanks,
- Arnaldo
reply other threads:[~2025-01-14 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Z4aO-4mkXi4ID7xs@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=namhyung@kernel.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