From: Andi Kleen <ak@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Stephane Eranian <eranian@google.com>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Vince Weaver <vincent.weaver@maine.edu>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [BUG] perf report --pid not reporting correctly
Date: Thu, 22 Sep 2016 07:57:23 -0700 [thread overview]
Message-ID: <20160922145723.GR3078@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAM9d7ch3bPnN2TH8JPdKf2pHxna2gOUJFbkus98zonJmqOehYA@mail.gmail.com>
> If not, I suggest to use --hierarchy mode with including the sort key
> as the first one. In this case. It'll still show absolute
> percentages of global total period, but you can see the desired result
> easily IMHO. Please try something like this:
>
> $ perf report --hierarchy -s pid,cpu
It would be nice if there was a way from scripts with a command line option
to ask hierarchy mode to only show a subset of the tree (e.g. with some
kind of pattern)
Then options like --pid could be obsoleted, but it would be far more
flexible and scale for all the sort keys which are supported, without
adding a lot of new command line options.
-Andi
prev parent reply other threads:[~2016-09-22 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 1:29 [BUG] perf report --pid not reporting correctly Stephane Eranian
2016-09-21 15:37 ` Arnaldo Carvalho de Melo
2016-09-21 16:34 ` Jiri Olsa
2016-09-21 20:18 ` Stephane Eranian
2016-09-22 1:34 ` Namhyung Kim
2016-09-22 2:22 ` Stephane Eranian
2016-09-22 3:20 ` Namhyung Kim
2016-09-22 13:36 ` Jiri Olsa
2016-09-23 3:31 ` Namhyung Kim
2016-09-22 0:14 ` Namhyung Kim
2016-09-22 14:57 ` Andi Kleen [this message]
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=20160922145723.GR3078@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=vincent.weaver@maine.edu \
/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.