From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v6 1/4] perf report: Fix incorrectly added dimensions as switch perf data file
Date: Mon, 23 Dec 2019 10:02:02 -0300 [thread overview]
Message-ID: <20191223130202.GD9076@kernel.org> (raw)
In-Reply-To: <7d517778-3edc-eeab-587a-ad09db978647@linux.intel.com>
Em Mon, Dec 23, 2019 at 08:55:00AM +0800, Jin, Yao escreveu:
>
>
> On 12/21/2019 12:34 AM, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Dec 20, 2019 at 09:37:19AM +0800, Jin Yao escreveu:
> > > We observed an issue that was some extra columns displayed after switching
> > > perf data file in browser. The steps to reproduce:
> > >
> > > 1. perf record -a -e cycles,instructions -- sleep 3
> > > 2. perf report --group
> > > 3. In browser, we use hotkey 's' to switch to another perf.data
> > > 4. Now in browser, the extra columns 'Self' and 'Children' are displayed.
> > >
> > > The issue is setup_sorting() executed again after repeat path, so dimensions
> > > are added again.
> > >
> > > This patch checks the last key returned from __cmd_report(). If it's
> > > K_SWITCH_INPUT_DATA, skips the setup_sorting().
> >
> > you forgot to add this right?
> >
> > Cc: Feng Tang <feng.tang@intel.com>
> > Fixes: ad0de0971b7f ("perf report: Enable the runtime switching of perf data file")
>
> Yes, I should add this in patch description. Thanks for reminding
>
> Do you need me to resend this patch-set (v7)?
Nope, I added it myself, thanks.
- Arnaldo
> Thanks
> Jin Yao
>
> > > v6:
> > > ---
> > > No change.
> > >
> > > v5:
> > > ---
> > > New patch in v5.
> > >
> > > Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
> > > ---
> > > tools/perf/builtin-report.c | 5 ++++-
> > > 1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> > > index 387311c67264..de988589d99b 100644
> > > --- a/tools/perf/builtin-report.c
> > > +++ b/tools/perf/builtin-report.c
> > > @@ -1076,6 +1076,7 @@ int cmd_report(int argc, const char **argv)
> > > struct stat st;
> > > bool has_br_stack = false;
> > > int branch_mode = -1;
> > > + int last_key = 0;
> > > bool branch_call_mode = false;
> > > #define CALLCHAIN_DEFAULT_OPT "graph,0.5,caller,function,percent"
> > > static const char report_callchain_help[] = "Display call graph (stack chain/backtrace):\n\n"
> > > @@ -1450,7 +1451,8 @@ int cmd_report(int argc, const char **argv)
> > > sort_order = sort_tmp;
> > > }
> > > - if (setup_sorting(session->evlist) < 0) {
> > > + if ((last_key != K_SWITCH_INPUT_DATA) &&
> > > + (setup_sorting(session->evlist) < 0)) {
> > > if (sort_order)
> > > parse_options_usage(report_usage, options, "s", 1);
> > > if (field_order)
> > > @@ -1530,6 +1532,7 @@ int cmd_report(int argc, const char **argv)
> > > ret = __cmd_report(&report);
> > > if (ret == K_SWITCH_INPUT_DATA) {
> > > perf_session__delete(session);
> > > + last_key = K_SWITCH_INPUT_DATA;
> > > goto repeat;
> > > } else
> > > ret = 0;
> > > --
> > > 2.17.1
> >
--
- Arnaldo
next prev parent reply other threads:[~2019-12-23 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 1:37 [PATCH v6 1/4] perf report: Fix incorrectly added dimensions as switch perf data file Jin Yao
2019-12-20 1:37 ` [PATCH v6 2/4] perf report: Change sort order by a specified event in group Jin Yao
2020-01-20 15:11 ` Jin, Yao
2019-12-20 1:37 ` [PATCH v6 3/4] perf report: Support a new key to reload the browser Jin Yao
2019-12-20 1:37 ` [PATCH v6 4/4] perf report: support hotkey to let user select any event for sorting Jin Yao
2019-12-20 13:53 ` [PATCH v6 1/4] perf report: Fix incorrectly added dimensions as switch perf data file Jiri Olsa
2019-12-20 16:34 ` Arnaldo Carvalho de Melo
2019-12-23 0:55 ` Jin, Yao
2019-12-23 13:02 ` Arnaldo Carvalho de Melo [this message]
2019-12-23 21:35 ` [tip: perf/urgent] " tip-bot2 for Jin Yao
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=20191223130202.GD9076@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.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 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.