From: sashiko-bot@kernel.org
To: "Thomas Falcon" <thomas.falcon@intel.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v8 5/6] perf tools: Show memory region in perf-script subcommand
Date: Thu, 10 Sep 2026 19:53:55 +0000 [thread overview]
Message-ID: <20260910195355.D6B651F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910194324.98002-6-thomas.falcon@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unnecessary full header inclusion of `session.h` in `mem-events.h` instead of a forward declaration.
--
commit 40386f8d2abdbd20961af3746935e85e6ef1913c
Author: Dapeng Mi <dapeng1.mi@linux.intel.com>
perf tools: Show memory region in perf-script subcommand
This commit adds a new memory region field to the perf-script output, sourced
from the mem_region field of the memory information data source. It also
incorporates fallback logic for pipe mode scenarios where feature bits might
not be available.
Link: https://lore.kernel.org/all/20260114011750.350569-1-dapeng1.mi@linux.intel.com/
[ ... ]
> diff --git a/tools/perf/util/mem-events.h b/tools/perf/util/mem-events.h
> index daa22748f9fea..4ebb8109fc3c4 100644
> --- a/tools/perf/util/mem-events.h
> +++ b/tools/perf/util/mem-events.h
> @@ -4,6 +4,7 @@
>
> #include <stdbool.h>
> #include <linux/types.h>
> +#include "session.h"
[Severity: Low]
Does this unnecessarily pull in the full session.h header when a forward
declaration would suffice?
According to the perf tools subsystem guidelines, it is preferred to use
forward declarations (e.g., "struct perf_session;") in header files instead
of full header inclusions when only structure pointer handles are referenced.
Since the new perf_script__meminfo_scnprintf() function prototype only needs a
pointer to struct perf_session, could this include be replaced with a forward
declaration to reduce header dependencies and namespace pollution? The full
include can then be placed directly in the .c files that dereference it.
>
> struct perf_mem_event {
> bool supported;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260910194324.98002-1-thomas.falcon@intel.com?part=5
next prev parent reply other threads:[~2026-09-10 19:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:43 [PATCH v8 0/6] perf: Add support for memory region/range reporting Thomas Falcon
2026-09-10 19:43 ` [PATCH v8 1/6] perf mem: Fix size tracking for mem_lvl's in perf_script__meminfo_scnprintf() Thomas Falcon
2026-09-10 19:55 ` sashiko-bot
2026-09-10 19:43 ` [PATCH v8 2/6] perf mem: Add support for printing PERF_MEM_LVLNUM_L0 Thomas Falcon
2026-09-10 19:51 ` sashiko-bot
2026-09-10 19:43 ` [PATCH v8 3/6] perf header: Support memory ranges Thomas Falcon
2026-09-10 19:58 ` sashiko-bot
2026-09-10 19:43 ` [PATCH v8 4/6] perf tools: Show memory region in perf-c2c subcommand Thomas Falcon
2026-09-10 19:54 ` sashiko-bot
2026-09-11 0:50 ` Mi, Dapeng
2026-09-11 15:58 ` Falcon, Thomas
2026-09-10 19:43 ` [PATCH v8 5/6] perf tools: Show memory region in perf-script subcommand Thomas Falcon
2026-09-10 19:53 ` sashiko-bot [this message]
2026-09-11 0:51 ` Mi, Dapeng
2026-09-10 19:43 ` [PATCH v8 6/6] perf c2c: print memory region data with stdio output Thomas Falcon
2026-09-10 19:59 ` 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=20260910195355.D6B651F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thomas.falcon@intel.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