From: Disha Goel <disgoel@linux.ibm.com>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
acme@kernel.org, jolsa@kernel.org, mpe@ellerman.id.au
Cc: maddy@linux.vnet.ibm.com, rnsastry@linux.ibm.com,
kjain@linux.ibm.com, linux-perf-users@vger.kernel.org,
disgoel@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] tools/perf: Fix aggr_printout to display cpu field irrespective of core value
Date: Fri, 16 Sep 2022 17:01:20 +0530 [thread overview]
Message-ID: <2353467d-c83d-f6ee-0972-1e94bc9f4f5d@linux.ibm.com> (raw)
In-Reply-To: <20220913115717.36191-1-atrajeev@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3923 bytes --]
On 9/13/22 5:27 PM, Athira Rajeev wrote:
> perf stat includes option to specify aggr_mode to display
> per-socket, per-core, per-die, per-node counter details.
> Also there is option -A ( AGGR_NONE, -no-aggr ), where the
> counter values are displayed for each cpu along with "CPU"
> value in one field of the output.
>
> Each of the aggregate mode uses the information fetched
> from "/sys/devices/system/cpu/cpuX/topology" like core_id,
> physical_package_id. Utility functions in "cpumap.c" fetches
> this information and populates the socket id, core id, cpu etc.
> If the platform does not expose the topology information,
> these values will be set to -1. Example, in case of powerpc,
> details like physical_package_id is restricted to be exposed
> in pSeries platform. So id.socket, id.core, id.cpu all will
> be set as -1.
>
> In case of displaying socket or die value, there is no check
> done in the "aggr_printout" function to see if it points to
> valid socket id or die. But for displaying "cpu" value, there
> is a check for "if (id.core > -1)". In case of powerpc pSeries
> where detail like physical_package_id is restricted to be
> exposed, id.core will be set to -1. Hence the column or field
> itself for CPU won't be displayed in the output.
>
> Result for per-socket:
>
> <<>>
> perf stat -e branches --per-socket -a true
>
> Performance counter stats for 'system wide':
>
> S-1 32 416,851 branches
> <<>>
>
> Here S has -1 in above result. But with -A option which also
> expects CPU in one column in the result, below is observed.
>
> <<>>
> /bin/perf stat -e instructions -A -a true
>
> Performance counter stats for 'system wide':
>
> 47,146 instructions
> 45,226 instructions
> 43,354 instructions
> 45,184 instructions
> <<>>
>
> If the cpu id value is pointing to -1 also, it makes sense
> to display the column in the output to replicate the behaviour
> or to be in precedence with other aggr options(like per-socket,
> per-core). Remove the check "id.core" so that CPU field gets
> displayed in the output.
>
> After the fix:
>
> <<>>
> perf stat -e instructions -A -a true
>
> Performance counter stats for 'system wide':
>
> CPU-1 64,034 instructions
> CPU-1 68,941 instructions
> CPU-1 59,418 instructions
> CPU-1 70,478 instructions
> CPU-1 65,201 instructions
> CPU-1 63,704 instructions
> <<>>
>
> This is caught while running "perf test" for
> "stat+json_output.sh" and "stat+csv_output.sh".
>
> Reported-by: Disha Goel<disgoel@linux.vnet.ibm.com>
> Signed-off-by: Athira Rajeev<atrajeev@linux.vnet.ibm.com>
Tested-by: Disha Goel<disgoel@linux.vnet.ibm.com>
> ---
> tools/perf/util/stat-display.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c
> index b82844cb0ce7..1b751a730271 100644
> --- a/tools/perf/util/stat-display.c
> +++ b/tools/perf/util/stat-display.c
> @@ -168,10 +168,9 @@ static void aggr_printout(struct perf_stat_config *config,
> id.socket,
> id.die,
> id.core);
> - } else if (id.core > -1) {
> + } else
> fprintf(config->output, "\"cpu\" : \"%d\", ",
> id.cpu.cpu);
> - }
> } else {
> if (evsel->percore && !config->percore_show_thread) {
> fprintf(config->output, "S%d-D%d-C%*d%s",
> @@ -179,11 +178,10 @@ static void aggr_printout(struct perf_stat_config *config,
> id.die,
> config->csv_output ? 0 : -3,
> id.core, config->csv_sep);
> - } else if (id.core > -1) {
> + } else
> fprintf(config->output, "CPU%*d%s",
> config->csv_output ? 0 : -7,
> id.cpu.cpu, config->csv_sep);
> - }
> }
> break;
> case AGGR_THREAD:
[-- Attachment #2: Type: text/html, Size: 4612 bytes --]
next prev parent reply other threads:[~2022-09-16 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 11:57 [PATCH] tools/perf: Fix aggr_printout to display cpu field irrespective of core value Athira Rajeev
2022-09-16 11:31 ` Disha Goel [this message]
2022-09-28 14:33 ` Athira Rajeev
2022-09-28 15:35 ` James Clark
2022-09-29 8:49 ` Athira Rajeev
2022-09-29 12:56 ` James Clark
2022-10-01 23:47 ` Ian Rogers
[not found] ` <993a1391ee931e859d972c460644d171@imap.linux.ibm.com>
2022-10-03 18:51 ` Ian Rogers
2022-10-04 7:06 ` Athira Rajeev
2022-10-04 14:49 ` Ian Rogers
2022-10-04 18:14 ` Arnaldo Carvalho de Melo
2022-10-04 18:14 ` Arnaldo Carvalho de Melo
2022-10-05 4:53 ` Athira Rajeev
2022-10-05 12:24 ` Arnaldo Carvalho de Melo
2022-10-05 12:28 ` Arnaldo Carvalho de Melo
2022-10-05 12:35 ` Arnaldo Carvalho de Melo
2022-10-06 12:46 ` Athira Rajeev
2022-10-06 14:03 ` Arnaldo Carvalho de Melo
2022-10-06 14:37 ` Athira Rajeev
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=2353467d-c83d-f6ee-0972-1e94bc9f4f5d@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rnsastry@linux.ibm.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).