From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
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: Thu, 6 Oct 2022 11:03:12 -0300 [thread overview]
Message-ID: <Yz7gIHyBhvR5UcaM@kernel.org> (raw)
In-Reply-To: <3D36EC01-B516-46CA-BC71-010617DB4A9D@linux.vnet.ibm.com>
Em Thu, Oct 06, 2022 at 06:16:14PM +0530, Athira Rajeev escreveu:
>
>
> > On 05-Oct-2022, at 6:05 PM, Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > Em Wed, Oct 05, 2022 at 09:28:52AM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Em Wed, Oct 05, 2022 at 10:23:39AM +0530, Athira Rajeev escreveu:
> >>> 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);
> >>> --
> >>> If it is confusing, shall I send it as a separate patch along with Tested-by from Ian ?
> >>
> >> I'll have to do this by hand, tried pointing b4 to this message and it
> >> picked the old one, also tried to save the message and apply by hand,
> >> its mangled.
> >
> > This is what I have now, will force push later, please triple check :-)
>
>
> Sorry for all the confusion Arnaldo. Hereafter, I will resubmit the patch to avoid this.
> In below patch which you shared, code change is correct. But commit message is different.
> So to avoid further confusion, I went ahead and posted a separate patch in the mailing list with:
>
> subject: [PATCH] tools/perf: Fix cpu check to use id.cpu.cpu in aggr_printout
> Patch link: https://lore.kernel.org/lkml/20221006114225.66303-1-atrajeev@linux.vnet.ibm.com/T/#u
>
> Please pick the separately send patch.
Ok, will do.
- Arnaldo
next prev parent reply other threads:[~2022-10-06 14:03 UTC|newest]
Thread overview: 17+ 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
[not found] ` <2353467d-c83d-f6ee-0972-1e94bc9f4f5d@linux.ibm.com>
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
[not found] ` <CAP-5=fU=bwv-e_53QagWsKvW8wjibOjfGvnivWFFVba5A55boA@mail.gmail.com>
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 [this message]
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=Yz7gIHyBhvR5UcaM@kernel.org \
--to=acme@kernel.org \
--cc=atrajeev@imap.linux.ibm.com \
--cc=atrajeev@linux.vnet.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: 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).