From: Alan Maguire <alan.maguire@oracle.com>
To: acme@kernel.org
Cc: dwarves@vger.kernel.org, jolsa@kernel.org, williams@redhat.com,
kcarcia@redhat.com, bpf@vger.kernel.org, kuifeng@fb.com,
linux@weissschuh.net, Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH dwarves 0/3] pahole: support nonstandard btf_features
Date: Tue, 16 Apr 2024 15:37:15 +0100 [thread overview]
Message-ID: <20240416143718.2857981-1-alan.maguire@oracle.com> (raw)
This small series allows the user to specify --btf_features=all along
with non-standard features such as --btf_features=reproducible_build .
Features are documented as standard - so participating in "all" -
or non-standard - such as "reproducible_build".
Tests are updated to use --btf_features=all,reproducible_build.
Series is applicable on next/ branch.
Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
Alan Maguire (3):
pahole: allow --btf_features to not participate in "all"
pahole: add reproducible_build to --btf_features
tests/reproducible_build: use --btf_features=all,reproducible_build
man-pages/pahole.1 | 10 +++++++++-
pahole.c | 37 ++++++++++++++++++++++++-------------
tests/reproducible_build.sh | 2 +-
3 files changed, 34 insertions(+), 15 deletions(-)
--
2.39.3
next reply other threads:[~2024-04-16 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 14:37 Alan Maguire [this message]
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
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=20240416143718.2857981-1-alan.maguire@oracle.com \
--to=alan.maguire@oracle.com \
--cc=acme@kernel.org \
--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).