From: Jiri Olsa <olsajiri@gmail.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: acme@kernel.org, quentin@isovalent.com, alan.maguire@oracle.com,
andrii.nakryiko@gmail.com, ast@kernel.org, daniel@iogearbox.net,
bpf@vger.kernel.org
Subject: Re: [PATCH dwarves v4 1/2] pahole: Add --btf_feature=decl_tag_kfuncs feature
Date: Tue, 6 Feb 2024 13:47:00 +0100 [thread overview]
Message-ID: <ZcIqRC1fOtZVv1Rk@krava> (raw)
In-Reply-To: <bd8f705a5c11b14571563a63045416233f9d06f1.1707071969.git.dxu@dxuuu.xyz>
On Sun, Feb 04, 2024 at 11:40:37AM -0700, Daniel Xu wrote:
> Add a feature flag to guard tagging of kfuncs. The next commit will
> implement the actual tagging.
>
> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
> ---
> btf_encoder.c | 2 ++
> dwarves.h | 1 +
> pahole.c | 1 +
> 3 files changed, 4 insertions(+)
we should update man page as well
also we need to update the kernel's scripts/Makefile.btf with
the new option for the next pahole version (1.26 I guess)
jirka
>
> diff --git a/btf_encoder.c b/btf_encoder.c
> index fd04008..e325f66 100644
> --- a/btf_encoder.c
> +++ b/btf_encoder.c
> @@ -77,6 +77,7 @@ struct btf_encoder {
> verbose,
> force,
> gen_floats,
> + tag_kfuncs,
> is_rel;
> uint32_t array_index_id;
> struct {
> @@ -1642,6 +1643,7 @@ struct btf_encoder *btf_encoder__new(struct cu *cu, const char *detached_filenam
> encoder->force = conf_load->btf_encode_force;
> encoder->gen_floats = conf_load->btf_gen_floats;
> encoder->skip_encoding_vars = conf_load->skip_encoding_btf_vars;
> + encoder->tag_kfuncs = conf_load->btf_decl_tag_kfuncs;
> encoder->verbose = verbose;
> encoder->has_index_type = false;
> encoder->need_index_type = false;
> diff --git a/dwarves.h b/dwarves.h
> index 857b37c..996eb70 100644
> --- a/dwarves.h
> +++ b/dwarves.h
> @@ -87,6 +87,7 @@ struct conf_load {
> bool skip_encoding_btf_vars;
> bool btf_gen_floats;
> bool btf_encode_force;
> + bool btf_decl_tag_kfuncs;
> uint8_t hashtable_bits;
> uint8_t max_hashtable_bits;
> uint16_t kabi_prefix_len;
> diff --git a/pahole.c b/pahole.c
> index 768a2fe..48c19b7 100644
> --- a/pahole.c
> +++ b/pahole.c
> @@ -1278,6 +1278,7 @@ struct btf_feature {
> BTF_FEATURE(enum64, skip_encoding_btf_enum64, true),
> BTF_FEATURE(optimized_func, btf_gen_optimized, false),
> BTF_FEATURE(consistent_func, skip_encoding_btf_inconsistent_proto, false),
> + BTF_FEATURE(decl_tag_kfuncs, btf_decl_tag_kfuncs, false),
> };
>
> #define BTF_MAX_FEATURE_STR 1024
> --
> 2.42.1
>
next prev parent reply other threads:[~2024-02-06 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 18:40 [PATCH dwarves v4 0/2] pahole: Inject kfunc decl tags into BTF Daniel Xu
2024-02-04 18:40 ` [PATCH dwarves v4 1/2] pahole: Add --btf_feature=decl_tag_kfuncs feature Daniel Xu
2024-02-06 12:47 ` Jiri Olsa [this message]
2024-02-06 14:14 ` Alan Maguire
2024-02-04 18:40 ` [PATCH dwarves v4 2/2] pahole: Inject kfunc decl tags into BTF Daniel Xu
2024-02-05 16:54 ` Eduard Zingerman
2024-02-05 23:31 ` Eduard Zingerman
2024-02-28 16:07 ` Daniel Xu
2024-02-28 21:33 ` Eduard Zingerman
2024-03-15 19:43 ` Daniel Xu
2024-02-08 10:00 ` Alan Maguire
2024-02-29 0:57 ` Daniel Xu
2024-03-13 3:17 ` Daniel Xu
2024-03-13 9:36 ` Alan Maguire
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=ZcIqRC1fOtZVv1Rk@krava \
--to=olsajiri@gmail.com \
--cc=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=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