From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: Daniel Xu <dxu@dxuuu.xyz>,
jolsa@kernel.org, quentin@isovalent.com,
andrii.nakryiko@gmail.com, ast@kernel.org, daniel@iogearbox.net,
bpf@vger.kernel.org
Subject: Re: [PATCH dwarves v3] pahole: Inject kfunc decl tags into BTF
Date: Mon, 29 Jan 2024 11:24:13 -0300 [thread overview]
Message-ID: <Zbe1DfHjhZHwIKha@kernel.org> (raw)
In-Reply-To: <49da8aff-1ec7-b908-2167-ee499e7a857a@oracle.com>
Em Mon, Jan 29, 2024 at 01:05:05PM +0000, Alan Maguire escreveu:
> This should probably be a BTF feature supported by --btf_features; that
> way we'd have a mechanism to switch it off if needed. Can you look at
> adding a "tag_kfunc" or whatever name suits into the btf_features[]
> array in pahole.c? Something like:
> BTF_FEATURE(tag_kfunc, btf_tag_kfunc, false),
> You'll also then need to add a btf_tag_kfunc boolean field to
> struct conf_load, and generation of kfunc tags should then be guarded by
> if (conf_load->btf_tag_kfunc)
> ...so that the tags are added conditionally depending on whether
> the user wants them.
> Then if a user specifies --btf_features=all or some subset of BTF
> features including "tag_kfunc" they will get kfunc tags.
Agreed.
> We probably should also move to using --btf_features instead of the
> current combination of "--" parameters when pahole is bumped to v1.26.
Alan, talking about that, I guess we better tag v1.26 before merging
this new kfunc work, wdyt?
- Arnaldo
next prev parent reply other threads:[~2024-01-29 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 1:30 [PATCH dwarves v3] pahole: Inject kfunc decl tags into BTF Daniel Xu
2024-01-29 13:05 ` Alan Maguire
2024-01-29 14:24 ` Arnaldo Carvalho de Melo [this message]
2024-01-29 16:15 ` Daniel Xu
2024-01-29 18:12 ` Alan Maguire
2024-01-31 10:17 ` Jiri Olsa
2024-02-04 18:08 ` Daniel Xu
2024-02-06 12:50 ` Jiri Olsa
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=Zbe1DfHjhZHwIKha@kernel.org \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=jolsa@kernel.org \
--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 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.