From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1] perf record: Refactor ARM64 leaf caller setup out of arch
Date: Thu, 07 May 2026 23:16:52 +0000 [thread overview]
Message-ID: <20260507231652.C7DAFC2BCB2@smtp.kernel.org> (raw)
In-Reply-To: <20260507170622.611933-1-irogers@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Orphaned function declaration `arch__add_leaf_frame_record_opts` left in `tools/perf/util/callchain.h`.
--
commit 9201ab7426a557fd23fbb8e0f9c2a95f023a9477
Author: Ian Rogers <irogers@google.com>
perf record: Refactor ARM64 leaf caller setup out of arch
Code in tools/perf/arch causes portability issues/opaqueness and LTO
issues due to the use of weak symbols. Move the adding of LR to the
sample_user_regs into arm64-frame-pointer-unwind-support.c conditional
on EM_HOST == EM_AARCH64.
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 4a5eba498c025..272bba7f4b9ec 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
[ ... ]
> @@ -3230,10 +3231,6 @@ static int record__parse_off_cpu_thresh(const struct option *opt,
> return 0;
> }
>
> -void __weak arch__add_leaf_frame_record_opts(struct record_opts *opts __maybe_unused)
> -{
> -}
> -
Since the weak definition and usage of arch__add_leaf_frame_record_opts()
are removed in this commit, should its declaration in
tools/perf/util/callchain.h also be removed to avoid leaving an orphaned
function declaration?
tools/perf/util/callchain.h:
[ ... ]
#endif
void arch__add_leaf_frame_record_opts(struct record_opts *opts);
char *callchain_list__sym_name(struct callchain_list *cl,
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260507170622.611933-1-irogers@google.com?part=1
next prev parent reply other threads:[~2026-05-07 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 17:06 [PATCH v1] perf record: Refactor ARM64 leaf caller setup out of arch Ian Rogers
2026-05-07 23:16 ` sashiko-bot [this message]
2026-05-08 10:35 ` James Clark
2026-05-12 5:41 ` [PATCH v2] " Ian Rogers
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=20260507231652.C7DAFC2BCB2@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=irogers@google.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko@lists.linux.dev \
/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