From: Athira Rajeev <atrajeev@linux.vnet.ibm.com> To: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Ian Rogers <irogers@google.com>, James Clark <james.clark@arm.com>, atrajeev <atrajeev@imap.linux.ibm.com>, maddy@linux.vnet.ibm.com, Nageswara Sastry <rnsastry@linux.ibm.com>, Kajol Jain <kjain@linux.ibm.com>, linux-perf-users <linux-perf-users@vger.kernel.org>, Jiri Olsa <jolsa@kernel.org>, Disha Goel <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: Wed, 5 Oct 2022 10:23:39 +0530 [thread overview] Message-ID: <137635B2-F4E8-4C65-B797-5C6511E265A8@linux.vnet.ibm.com> (raw) In-Reply-To: <Yzx4ET7QU2VpCcsx@kernel.org> > On 04-Oct-2022, at 11:44 PM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote: > > Em Tue, Oct 04, 2022 at 03:14:27PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Tue, Oct 04, 2022 at 07:49:21AM -0700, Ian Rogers escreveu: >>> On Tue, Oct 4, 2022, 12:06 AM Athira Rajeev <atrajeev@linux.vnet.ibm.com> >>>> Thanks for helping with testing. Can I add your Tested-by for the patch ? >> >>> Yep. >> >>> Tested-by: Ian Rogers <irogers@google.com> > > > Thanks, applied. > > - Arnaldo Hi Arnaldo, Looks like you have taken change to remove id.core check: https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=tmp.perf/core&id=db83f447b323958cdc5fedcf2134effb2ec9a6fe But the patch that has to go in is : "[PATCH] tools/perf: Fix cpu check to use id.cpu.cpu in ggr_printout" which is tested by Ian and "pasted" by me in same mail thread. Re-pasting here for reference: From 4dd98d953940deb2f85176cb6b4ecbfd18dbdbf9 Mon Sep 17 00:00:00 2001 From: Athira Rajeev <atrajeev@linux.vnet.ibm.com> Date: Mon, 3 Oct 2022 15:47:27 +0530 Subject: [PATCH] tools/perf: Fix cpu check to use id.cpu.cpu in aggr_printout perf stat has options to aggregate the counts in different modes like per socket, per core etc. The function "aggr_printout" in util/stat-display.c which is used to print the aggregates, has a check for cpu in case of AGGR_NONE. This check was originally using condition : "if (id.cpu.cpu > -1)". But this got changed after commit df936cadfb58 ("perf stat: Add JSON output option"), which added option to output json format for different aggregation modes. After this commit, the check in "aggr_printout" is using "if (id.core > -1)". The old code was using "id.cpu.cpu > -1" while the new code is using "id.core > -1". But since the value printed is id.cpu.cpu, fix this check to use cpu and not core. Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com> Suggested-by: James Clark <james.clark@arm.com> Suggested-by: Ian Rogers <irogers@google.com> --- tools/perf/util/stat-display.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c index b82844cb0ce7..cf28020798ec 100644 --- a/tools/perf/util/stat-display.c +++ b/tools/perf/util/stat-display.c @@ -168,7 +168,7 @@ static void aggr_printout(struct perf_stat_config *config, id.socket, id.die, id.core); - } else if (id.core > -1) { + } else if (id.cpu.cpu > -1) { fprintf(config->output, "\"cpu\" : \"%d\", ", id.cpu.cpu); } @@ -179,7 +179,7 @@ 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 if (id.cpu.cpu > -1) { fprintf(config->output, "CPU%*d%s", config->csv_output ? 0 : -7, id.cpu.cpu, config->csv_sep); -- 2.31.1 If it is confusing, shall I send it as a separate patch along with Tested-by from Ian ? Please revert https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=tmp.perf/core&id=db83f447b323958cdc5fedcf2134effb2ec9a6fe Thanks Athira >
WARNING: multiple messages have this Message-ID (diff)
From: Athira Rajeev <atrajeev@linux.vnet.ibm.com> To: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Ian Rogers <irogers@google.com>, maddy@linux.vnet.ibm.com, Nageswara Sastry <rnsastry@linux.ibm.com>, Kajol Jain <kjain@linux.ibm.com>, linux-perf-users <linux-perf-users@vger.kernel.org>, James Clark <james.clark@arm.com>, Jiri Olsa <jolsa@kernel.org>, atrajeev <atrajeev@imap.linux.ibm.com>, Disha Goel <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: Wed, 5 Oct 2022 10:23:39 +0530 [thread overview] Message-ID: <137635B2-F4E8-4C65-B797-5C6511E265A8@linux.vnet.ibm.com> (raw) In-Reply-To: <Yzx4ET7QU2VpCcsx@kernel.org> > On 04-Oct-2022, at 11:44 PM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote: > > Em Tue, Oct 04, 2022 at 03:14:27PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Tue, Oct 04, 2022 at 07:49:21AM -0700, Ian Rogers escreveu: >>> On Tue, Oct 4, 2022, 12:06 AM Athira Rajeev <atrajeev@linux.vnet.ibm.com> >>>> Thanks for helping with testing. Can I add your Tested-by for the patch ? >> >>> Yep. >> >>> Tested-by: Ian Rogers <irogers@google.com> > > > Thanks, applied. > > - Arnaldo Hi Arnaldo, Looks like you have taken change to remove id.core check: https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=tmp.perf/core&id=db83f447b323958cdc5fedcf2134effb2ec9a6fe But the patch that has to go in is : "[PATCH] tools/perf: Fix cpu check to use id.cpu.cpu in ggr_printout" which is tested by Ian and "pasted" by me in same mail thread. Re-pasting here for reference: From 4dd98d953940deb2f85176cb6b4ecbfd18dbdbf9 Mon Sep 17 00:00:00 2001 From: Athira Rajeev <atrajeev@linux.vnet.ibm.com> Date: Mon, 3 Oct 2022 15:47:27 +0530 Subject: [PATCH] tools/perf: Fix cpu check to use id.cpu.cpu in aggr_printout perf stat has options to aggregate the counts in different modes like per socket, per core etc. The function "aggr_printout" in util/stat-display.c which is used to print the aggregates, has a check for cpu in case of AGGR_NONE. This check was originally using condition : "if (id.cpu.cpu > -1)". But this got changed after commit df936cadfb58 ("perf stat: Add JSON output option"), which added option to output json format for different aggregation modes. After this commit, the check in "aggr_printout" is using "if (id.core > -1)". The old code was using "id.cpu.cpu > -1" while the new code is using "id.core > -1". But since the value printed is id.cpu.cpu, fix this check to use cpu and not core. Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com> Suggested-by: James Clark <james.clark@arm.com> Suggested-by: Ian Rogers <irogers@google.com> --- tools/perf/util/stat-display.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/perf/util/stat-display.c b/tools/perf/util/stat-display.c index b82844cb0ce7..cf28020798ec 100644 --- a/tools/perf/util/stat-display.c +++ b/tools/perf/util/stat-display.c @@ -168,7 +168,7 @@ static void aggr_printout(struct perf_stat_config *config, id.socket, id.die, id.core); - } else if (id.core > -1) { + } else if (id.cpu.cpu > -1) { fprintf(config->output, "\"cpu\" : \"%d\", ", id.cpu.cpu); } @@ -179,7 +179,7 @@ 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 if (id.cpu.cpu > -1) { fprintf(config->output, "CPU%*d%s", config->csv_output ? 0 : -7, id.cpu.cpu, config->csv_sep); -- 2.31.1 If it is confusing, shall I send it as a separate patch along with Tested-by from Ian ? Please revert https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=tmp.perf/core&id=db83f447b323958cdc5fedcf2134effb2ec9a6fe Thanks Athira >
next prev parent reply other threads:[~2022-10-05 4:54 UTC|newest] Thread overview: 30+ 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-13 11:57 ` Athira Rajeev 2022-09-16 11:31 ` Disha Goel 2022-09-28 14:33 ` Athira Rajeev 2022-09-28 15:35 ` James Clark 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 2022-10-01 23:47 ` Ian Rogers [not found] ` <993a1391ee931e859d972c460644d171@imap.linux.ibm.com> 2022-10-03 18:51 ` Ian Rogers 2022-10-03 18:51 ` Ian Rogers 2022-10-04 7:06 ` Athira Rajeev 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-04 18:14 ` Arnaldo Carvalho de Melo 2022-10-04 18:14 ` Arnaldo Carvalho de Melo 2022-10-05 4:53 ` Athira Rajeev [this message] 2022-10-05 4:53 ` Athira Rajeev 2022-10-05 12:24 ` Arnaldo Carvalho de Melo 2022-10-05 12:24 ` Arnaldo Carvalho de Melo 2022-10-05 12:28 ` Arnaldo Carvalho de Melo 2022-10-05 12:28 ` Arnaldo Carvalho de Melo 2022-10-05 12:35 ` 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=137635B2-F4E8-4C65-B797-5C6511E265A8@linux.vnet.ibm.com \ --to=atrajeev@linux.vnet.ibm.com \ --cc=acme@kernel.org \ --cc=atrajeev@imap.linux.ibm.com \ --cc=disgoel@linux.vnet.ibm.com \ --cc=irogers@google.com \ --cc=james.clark@arm.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=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: linkBe 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.