From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: jolsa@kernel.org, quentin@isovalent.com, alan.maguire@oracle.com,
eddyz87@gmail.com, andrii.nakryiko@gmail.com, ast@kernel.org,
daniel@iogearbox.net, bpf@vger.kernel.org
Subject: Re: [PATCH dwarves v9 2/3] pahole: Add --btf_feature=decl_tag_kfuncs feature
Date: Tue, 30 Apr 2024 15:48:06 -0300 [thread overview]
Message-ID: <ZjE85q0SJ1sve25u@x1> (raw)
In-Reply-To: <6d69d6dce917475ffe9c1bd7bc53358904f60915.1714430735.git.dxu@dxuuu.xyz>
On Mon, Apr 29, 2024 at 04:45:59PM -0600, Daniel Xu wrote:
> Add a feature flag to guard tagging of kfuncs. The next commit will
> implement the actual tagging.
>
> Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
Also 'decl_tag_kfuncs' is not enabled when using --btf_features=default,
right? as:
BTF_DEFAULT_FEATURE(decl_tag_kfuncs, btf_decl_tag_kfuncs, false),
And that false is .default_enabled=false.
So I added:
diff --git a/man-pages/pahole.1 b/man-pages/pahole.1
index be04f1c617291e21..f0605935a9f1b4dc 100644
--- a/man-pages/pahole.1
+++ b/man-pages/pahole.1
@@ -308,7 +308,6 @@ Encode BTF using the specified feature list, or specify 'default' for all standa
in some CUs and not others, or when the same
function name has inconsistent BTF descriptions
in different CUs.
- decl_tag_kfuncs Inject a BTF_KIND_DECL_TAG for each discovered kfunc.
.fi
Supported non-standard features (not enabled for 'default')
@@ -317,6 +316,7 @@ Supported non-standard features (not enabled for 'default')
reproducible_build Ensure generated BTF is consistent every time;
without this parallel BTF encoding can result in
inconsistent BTF ids.
+ decl_tag_kfuncs Inject a BTF_KIND_DECL_TAG for each discovered kfunc.
.fi
So for example, specifying \-\-btf_encode=var,enum64 will result in a BTF encoding that (as well as encoding basic BTF information) will contain variables and enum64 values.
----
Please ack. Alan, please check if your Reviewed-by stands with the above
change.
Thanks,
- Arnaldo
> ---
> btf_encoder.c | 2 ++
> dwarves.h | 1 +
> man-pages/pahole.1 | 1 +
> pahole.c | 1 +
> 4 files changed, 5 insertions(+)
>
> diff --git a/btf_encoder.c b/btf_encoder.c
> index 5ffaf5d..f0ef20a 100644
> --- a/btf_encoder.c
> +++ b/btf_encoder.c
> @@ -76,6 +76,7 @@ struct btf_encoder {
> verbose,
> force,
> gen_floats,
> + tag_kfuncs,
> is_rel;
> uint32_t array_index_id;
> struct {
> @@ -1661,6 +1662,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 dd35a4e..7d566b6 100644
> --- a/dwarves.h
> +++ b/dwarves.h
> @@ -94,6 +94,7 @@ struct conf_load {
> bool btf_gen_floats;
> bool btf_encode_force;
> bool reproducible_build;
> + bool btf_decl_tag_kfuncs;
> uint8_t hashtable_bits;
> uint8_t max_hashtable_bits;
> uint16_t kabi_prefix_len;
> diff --git a/man-pages/pahole.1 b/man-pages/pahole.1
> index e3c58e0..4769b58 100644
> --- a/man-pages/pahole.1
> +++ b/man-pages/pahole.1
> @@ -308,6 +308,7 @@ Encode BTF using the specified feature list, or specify 'default' for all standa
> in some CUs and not others, or when the same
> function name has inconsistent BTF descriptions
> in different CUs.
> + decl_tag_kfuncs Inject a BTF_KIND_DECL_TAG for each discovered kfunc.
> .fi
>
> Supported non-standard features (not enabled for 'default')
> diff --git a/pahole.c b/pahole.c
> index 750b847..954498d 100644
> --- a/pahole.c
> +++ b/pahole.c
> @@ -1289,6 +1289,7 @@ struct btf_feature {
> BTF_DEFAULT_FEATURE(enum64, skip_encoding_btf_enum64, true),
> BTF_DEFAULT_FEATURE(optimized_func, btf_gen_optimized, false),
> BTF_DEFAULT_FEATURE(consistent_func, skip_encoding_btf_inconsistent_proto, false),
> + BTF_DEFAULT_FEATURE(decl_tag_kfuncs, btf_decl_tag_kfuncs, false),
> BTF_NON_DEFAULT_FEATURE(reproducible_build, reproducible_build, false),
> };
>
> --
> 2.44.0
next prev parent reply other threads:[~2024-04-30 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 22:45 [PATCH dwarves v9 0/3] pahole: Inject kfunc decl tags into BTF Daniel Xu
2024-04-29 22:45 ` [PATCH dwarves v9 1/3] pahole: Save input filename separate from output Daniel Xu
2024-04-30 18:41 ` Arnaldo Carvalho de Melo
2024-04-29 22:45 ` [PATCH dwarves v9 2/3] pahole: Add --btf_feature=decl_tag_kfuncs feature Daniel Xu
2024-04-30 18:48 ` Arnaldo Carvalho de Melo [this message]
2024-04-30 23:00 ` Daniel Xu
2024-05-02 11:49 ` Alan Maguire
2024-05-02 13:35 ` Arnaldo Carvalho de Melo
2024-05-02 13:43 ` Alan Maguire
2024-04-29 22:46 ` [PATCH dwarves v9 3/3] pahole: Inject kfunc decl tags into BTF Daniel Xu
2024-04-30 19:57 ` Arnaldo Carvalho de Melo
2024-04-30 23:29 ` Daniel Xu
2024-04-30 20:42 ` Arnaldo Carvalho de Melo
2024-04-30 23:27 ` Daniel Xu
2024-05-06 20:07 ` Arnaldo Carvalho de Melo
2024-05-07 2:18 ` 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=ZjE85q0SJ1sve25u@x1 \
--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=eddyz87@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox