From: Daniel Xu <dxu@dxuuu.xyz>
To: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kbuild@vger.kernel.org, andrii@kernel.org,
olsajiri@gmail.com, quentin@isovalent.com,
alan.maguire@oracle.com, acme@kernel.org, eddyz87@gmail.com
Cc: kernel-team@meta.com
Subject: [PATCH bpf-next v3 0/2] bpf: bpftool: Support dumping kfunc prototypes from BTF
Date: Mon, 13 May 2024 12:38:57 -0600 [thread overview]
Message-ID: <cover.1715625447.git.dxu@dxuuu.xyz> (raw)
This patchset enables both detecting as well as dumping compilable
prototypes for kfuncs.
Users will be able to look at BTF inside vmlinux (or modules) and check
if the kfunc they want is available.
For developer convenience, we also support dumping kfunc prototypes from
bpftool.
=== Changelog ===
From v2:
* Update Makefile.btf with pahole flag
* More error checking
* Output formatting changes
* Drop already-merged commit
From v1:
* Add __weak annotation
* Use btf_dump for kfunc prototypes
* Update kernel bpf_rdonly_cast() signature
Daniel Xu (2):
kbuild: bpf: Tell pahole to DECL_TAG kfuncs
bpftool: Support dumping kfunc prototypes from BTF
scripts/Makefile.btf | 2 +-
tools/bpf/bpftool/btf.c | 54 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 55 insertions(+), 1 deletion(-)
--
2.44.0
next reply other threads:[~2024-05-13 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 18:38 Daniel Xu [this message]
2024-05-13 18:38 ` [PATCH bpf-next v3 1/2] kbuild: bpf: Tell pahole to DECL_TAG kfuncs Daniel Xu
2024-05-13 18:38 ` [PATCH bpf-next v3 2/2] bpftool: Support dumping kfunc prototypes from BTF Daniel Xu
2024-05-13 21:14 ` Daniel Xu
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=cover.1715625447.git.dxu@dxuuu.xyz \
--to=dxu@dxuuu.xyz \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=quentin@isovalent.com \
/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