From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: acme@kernel.org, dwarves@vger.kernel.org, jolsa@kernel.org,
williams@redhat.com, kcarcia@redhat.com, bpf@vger.kernel.org,
kuifeng@fb.com, linux@weissschuh.net
Subject: Re: [PATCH dwarves 1/3] pahole: allow --btf_features to not participate in "all"
Date: Thu, 18 Apr 2024 17:06:32 -0700 [thread overview]
Message-ID: <CAEf4BzaS9_x+0DPuHU4NAFEP1+Mb-RPdmMfVCw9oW-d=Lj-cmg@mail.gmail.com> (raw)
In-Reply-To: <20240416143718.2857981-2-alan.maguire@oracle.com>
On Tue, Apr 16, 2024 at 7:38 AM Alan Maguire <alan.maguire@oracle.com> wrote:
>
> Specifying --btf_features=all enables all supported BTF features.
> However there are some features that are non-standard, so we should
> support a way to use them in --btf_features but not participate in
> the set of features enabled by "--btf_features=all". As part of this,
> also support all used in a list of --btf_features, i.e.
>
> --btf_features=all,nonstandard_feature
>
> Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
> ---
> man-pages/pahole.1 | 2 +-
> pahole.c | 36 +++++++++++++++++++++++-------------
> 2 files changed, 24 insertions(+), 14 deletions(-)
>
> diff --git a/man-pages/pahole.1 b/man-pages/pahole.1
> index 2be165d..2c08e97 100644
> --- a/man-pages/pahole.1
> +++ b/man-pages/pahole.1
> @@ -290,7 +290,7 @@ Allow using all the BTF features supported by pahole.
>
> .TP
> .B \-\-btf_features=FEATURE_LIST
> -Encode BTF using the specified feature list, or specify 'all' for all features supported. This option can be used as an alternative to unsing multiple BTF-related options. Supported features are
> +Encode BTF using the specified feature list, or specify 'all' for all standard features supported. This option can be used as an alternative to unsing multiple BTF-related options. Supported standard features are
>
> .nf
> encode_force Ignore invalid symbols when encoding BTF; for example
> diff --git a/pahole.c b/pahole.c
> index 77772bb..890ef81 100644
> --- a/pahole.c
> +++ b/pahole.c
> @@ -1266,23 +1266,26 @@ ARGP_PROGRAM_VERSION_HOOK_DEF = dwarves_print_version;
> * BTF encoding apply; we encode type/decl tags, do not encode
> * floats, etc. This ensures backwards compatibility.
> */
> -#define BTF_FEATURE(name, alias, default_value) \
> - { #name, #alias, &conf_load.alias, default_value }
> +#define BTF_FEATURE(name, alias, default_value, enable_for_all) \
> + { #name, #alias, &conf_load.alias, default_value, enable_for_all }
>
> struct btf_feature {
> const char *name;
> const char *option_alias;
> bool *conf_value;
> bool default_value;
> + bool enable_for_all; /* some nonstandard features may not
> + * be enabled for --btf_features=all
> + */
> } btf_features[] = {
> - BTF_FEATURE(encode_force, btf_encode_force, false),
> - BTF_FEATURE(var, skip_encoding_btf_vars, true),
> - BTF_FEATURE(float, btf_gen_floats, false),
> - BTF_FEATURE(decl_tag, skip_encoding_btf_decl_tag, true),
> - BTF_FEATURE(type_tag, skip_encoding_btf_type_tag, true),
> - 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(encode_force, btf_encode_force, false, true),
> + BTF_FEATURE(var, skip_encoding_btf_vars, true, true),
> + BTF_FEATURE(float, btf_gen_floats, false, true),
> + BTF_FEATURE(decl_tag, skip_encoding_btf_decl_tag, true, true),
> + BTF_FEATURE(type_tag, skip_encoding_btf_type_tag, true, true),
> + BTF_FEATURE(enum64, skip_encoding_btf_enum64, true, true),
> + BTF_FEATURE(optimized_func, btf_gen_optimized, false, true),
> + BTF_FEATURE(consistent_func, skip_encoding_btf_inconsistent_proto, false, true),
> };
maybe keep those special features in a separate array instead?
it is kind of weird to see --btf_features=all,and_then_some, maybe it
makes sense to have --btf_extras or something for those?
>
> #define BTF_MAX_FEATURE_STR 1024
> @@ -1350,8 +1353,10 @@ static void parse_btf_features(const char *features, bool strict)
> if (strcmp(features, "all") == 0) {
> int i;
>
> - for (i = 0; i < ARRAY_SIZE(btf_features); i++)
> - enable_btf_feature(&btf_features[i]);
> + for (i = 0; i < ARRAY_SIZE(btf_features); i++) {
> + if (btf_features[i].enable_for_all)
> + enable_btf_feature(&btf_features[i]);
> + }
> return;
> }
>
> @@ -1361,7 +1366,12 @@ static void parse_btf_features(const char *features, bool strict)
> struct btf_feature *feature = find_btf_feature(feature_name);
>
> if (!feature) {
> - if (strict) {
> + /* --btf_features=all,nonstandard_feature should be
> + * allowed.
> + */
> + if (strcmp(feature_name, "all") == 0) {
> + parse_btf_features(feature_name, strict);
> + } else if (strict) {
> fprintf(stderr, "Feature '%s' in '%s' is not supported. Supported BTF features are:\n",
> feature_name, features);
> show_supported_btf_features(stderr);
> --
> 2.39.3
>
>
next prev parent reply other threads:[~2024-04-19 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:37 [PATCH dwarves 0/3] pahole: support nonstandard btf_features Alan Maguire
2024-04-16 14:37 ` [PATCH dwarves 1/3] pahole: allow --btf_features to not participate in "all" Alan Maguire
2024-04-19 0:06 ` Andrii Nakryiko [this message]
2024-04-19 9:44 ` Alan Maguire
2024-04-16 14:37 ` [PATCH dwarves 2/3] pahole: add reproducible_build to --btf_features Alan Maguire
2024-04-16 15:24 ` Arnaldo Carvalho de Melo
2024-04-16 15:41 ` Alan Maguire
2024-04-16 20:44 ` Arnaldo Carvalho de Melo
2024-04-16 14:37 ` [PATCH dwarves 3/3] tests/reproducible_build: use --btf_features=all,reproducible_build 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='CAEf4BzaS9_x+0DPuHU4NAFEP1+Mb-RPdmMfVCw9oW-d=Lj-cmg@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=kcarcia@redhat.com \
--cc=kuifeng@fb.com \
--cc=linux@weissschuh.net \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).