From: sashiko-bot@kernel.org
To: "Athira Rajeev" <atrajeev@linux.ibm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V4 1/6] tools/perf: Move powerpc VPA-DTL auxtrace init into a separate file
Date: Wed, 29 Jul 2026 12:55:39 +0000 [thread overview]
Message-ID: <20260729125540.629FC1F00ADB@smtp.kernel.org> (raw)
In-Reply-To: <20260729124400.65009-2-atrajeev@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing forward declarations for `struct evsel` and `struct auxtrace_record` in `powerpc-vpadtl.h`.
--
--- Patch [1]: [PATCH V4 1/6] tools/perf: Move powerpc VPA-DTL auxtrace init into a separate file ---
commit d6642397942d2744eabc1f173cb06052b8c22930
Author: Athira Rajeev <atrajeev@linux.ibm.com>
tools/perf: Move powerpc VPA-DTL auxtrace init into a separate file
This commit factors out the VPA-DTL auxtrace recording initialization logic
from auxtrace.c into a new file, vpa-dtl.c. It reduces auxtrace.c to a thin
dispatcher that calls per-PMU init functions like vpa_dtl_recording_init().
This preparation aims to accommodate additional PMUs like HTM without
creating a monolithic file.
[ ... ]
> diff --git a/tools/perf/util/powerpc-vpadtl.h b/tools/perf/util/powerpc-vpadtl.h
> index ca809660b9bb7..41e09b17a353d 100644
> --- a/tools/perf/util/powerpc-vpadtl.h
> +++ b/tools/perf/util/powerpc-vpadtl.h
> @@ -20,4 +20,5 @@ struct perf_pmu;
> int powerpc_vpadtl_process_auxtrace_info(union perf_event *event,
> struct perf_session *session);
>
> +struct auxtrace_record *vpa_dtl_recording_init(struct evsel *pos, int *err);
[Severity: Low]
This isn't a bug, but could we add forward declarations for struct evsel and
struct auxtrace_record before they are used in this function prototype?
Without prior declarations, using undeclared structures in a function
parameter list gives them function prototype scope in C. While the current
inclusion order in the source files hides the issue, this could cause
compiler warnings about structures declared inside a parameter list, or
build failures if this header is included in a different context. Adding
forward declarations here would also align with the perf subsystem guidelines
for header files.
> #endif
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729124400.65009-1-atrajeev@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-07-29 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 12:43 [PATCH V4 0/6] tools/perf: Add powerpc HTM auxtrace support Athira Rajeev
2026-07-29 12:43 ` [PATCH V4 1/6] tools/perf: Move powerpc VPA-DTL auxtrace init into a separate file Athira Rajeev
2026-07-29 12:55 ` sashiko-bot [this message]
2026-07-29 12:43 ` [PATCH V4 2/6] tools/perf: Add AUXTRACE recording support for powerpc HTM Athira Rajeev
2026-07-29 13:02 ` sashiko-bot
2026-07-29 12:43 ` [PATCH V4 3/6] tools/perf: Add arch hook to drain remaining data before event close Athira Rajeev
2026-07-29 12:56 ` sashiko-bot
2026-07-29 12:43 ` [PATCH V4 4/6] tools/perf: Add powerpc callback support for arch_perf_record__need_read Athira Rajeev
2026-07-29 13:00 ` sashiko-bot
2026-07-29 12:43 ` [PATCH V4 5/6] tools/perf: Add powerpc HTM auxtrace event processing support Athira Rajeev
2026-07-29 12:44 ` [PATCH V4 6/6] tools/perf: Add perf tool support for processing powerpc HTM AUXTRACE records Athira Rajeev
2026-07-29 12:55 ` sashiko-bot
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=20260729125540.629FC1F00ADB@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=atrajeev@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.