From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>,
Pekka Enberg <penberg@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 3/3] perf report: Add --show-time-info option
Date: Mon, 02 Dec 2013 23:38:20 +0900 [thread overview]
Message-ID: <1385995100.1710.11.camel@leonhard> (raw)
In-Reply-To: <20131202123347.GD2371@ghostprotocols.net>
Hi Arnaldo,
2013-12-02 (월), 09:33 -0300, Arnaldo Carvalho de Melo:
> Em Mon, Dec 02, 2013 at 03:53:19PM +0900, Namhyung Kim escreveu:
> > From: Namhyung Kim <namhyung.kim@lge.com>
> >
> > The --show-time-info option is for displaying elapsed sampling time
>
> Isn't that too long? Can't we use just --time/-t?
Hmm.. interesting. Your previous feedback was to use longer and clearer
option name. :)
https://lkml.org/lkml/2013/11/18/198
>
> > information for each entry.
> >
> > $ perf record -- perf bench sched messaging
> > $ perf report --stdio --show-time-info
> > ...
> > # Samples: 10K of event 'cycles'
> > # Event count (approx.): 5118793536
> > # Total sampling time : 0.184277 (sec)
> > #
> > # Overhead Time Command Shared Object Symbol
> > # ........ .......... ............... ................. ...........................
> > #
> > 7.26% 0.007413 sched-messaging [unknown] [.] 0x0000003153e7a6e7
> > 4.79% 0.006088 sched-messaging [kernel.kallsyms] [k] avc_has_perm_flags
> > 4.38% 0.004809 sched-messaging [kernel.kallsyms] [k] copy_user_generic_string
> > 3.81% 0.005457 sched-messaging [kernel.kallsyms] [k] _raw_spin_lock
> > 2.92% 0.002745 sched-messaging [kernel.kallsyms] [k] _raw_spin_lock_irqsave
> > 2.72% 0.002896 sched-messaging [kernel.kallsyms] [k] unix_stream_recvmsg
> > 2.55% 0.003745 sched-messaging [kernel.kallsyms] [k] __slab_free
> > 2.45% 0.002807 sched-messaging [kernel.kallsyms] [k] page_fault
> > 2.08% 0.002258 sched-messaging [kernel.kallsyms] [k] sock_has_perm
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/builtin-report.c | 2 ++
> > tools/perf/ui/hist.c | 68 +++++++++++++++++++++++++++++++++++++--------
> > tools/perf/util/hist.h | 1 +
> > tools/perf/util/symbol.h | 3 +-
> > 4 files changed, 62 insertions(+), 12 deletions(-)
> >
> > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c
> > index eb849e9f7093..345cce6f5fa2 100644
> > --- a/tools/perf/builtin-report.c
> > +++ b/tools/perf/builtin-report.c
> > @@ -898,6 +898,8 @@ int cmd_report(int argc, const char **argv, const char *prefix __maybe_unused)
> > OPT_BOOLEAN(0, "mem-mode", &report.mem_mode, "mem access profile"),
> > OPT_CALLBACK(0, "percent-limit", &report, "percent",
> > "Don't show entries under that percent", parse_percent_limit),
> > + OPT_BOOLEAN(0, "show-time-info", &symbol_conf.show_time_info,
> > + "Show a column with the elapsed time"),
> > OPT_END()
> > };
> > struct perf_data_file file = {
> > diff --git a/tools/perf/ui/hist.c b/tools/perf/ui/hist.c
> > index 78f4c92e9b73..7cf584a0bb61 100644
> > --- a/tools/perf/ui/hist.c
> > +++ b/tools/perf/ui/hist.c
> > @@ -7,19 +7,24 @@
> > #include "../util/evsel.h"
> >
> > /* hist period print (hpp) functions */
> > +enum hpp_fmt_type {
> > + HPP_FMT__PERCENT,
> > + HPP_FMT__RAW,
> > + HPP_FMT__TIME,
> > +};
>
> I wonder if we can't make this a bitmask... Does it make sense to print
> both percent and time, for instance?
I'm not sure I understood you correctly, but did you mean printing both
percent and time in a single column? This enum and the __hpp_fmt()
function is for a single column. I can add a new column for time
percent if you want.
Thanks,
Namhyung
next prev parent reply other threads:[~2013-12-02 14:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 6:53 [RFC 0/3] perf tools: Show time info (v1) Namhyung Kim
2013-12-02 6:53 ` [PATCH 1/3] perf tools: Record total sampling time Namhyung Kim
2013-12-02 12:45 ` Ingo Molnar
2013-12-02 12:57 ` Ingo Molnar
2013-12-02 15:43 ` Namhyung Kim
2013-12-02 16:36 ` Ingo Molnar
2013-12-02 20:24 ` Arnaldo Carvalho de Melo
2013-12-03 5:44 ` Namhyung Kim
2013-12-03 14:30 ` David Ahern
2013-12-04 10:00 ` Ingo Molnar
2013-12-04 10:02 ` Ingo Molnar
2013-12-03 5:33 ` Namhyung Kim
2013-12-02 15:05 ` Namhyung Kim
2013-12-02 18:51 ` Arnaldo Carvalho de Melo
2013-12-02 6:53 ` [PATCH 2/3] perf tools: Record sampling time for each entry Namhyung Kim
2013-12-02 12:39 ` Arnaldo Carvalho de Melo
2013-12-02 14:57 ` Namhyung Kim
2013-12-02 18:49 ` Arnaldo Carvalho de Melo
2013-12-03 4:33 ` Namhyung Kim
2013-12-02 6:53 ` [PATCH 3/3] perf report: Add --show-time-info option Namhyung Kim
2013-12-02 12:33 ` Arnaldo Carvalho de Melo
2013-12-02 14:38 ` Namhyung Kim [this message]
2013-12-02 9:35 ` [RFC 0/3] perf tools: Show time info (v1) Pekka Enberg
2013-12-03 2:28 ` Namhyung Kim
2013-12-02 17:04 ` Andi Kleen
2013-12-03 2:34 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2013-12-02 19:23 [PATCH 3/3] perf report: Add --show-time-info option Arnaldo Carvalho de Melo
2013-12-02 19:25 ` David Ahern
2013-12-02 19:38 ` Arnaldo Carvalho de Melo
2013-12-02 19:58 ` David Ahern
2013-12-02 20:17 ` Arnaldo Carvalho de Melo
2013-12-02 20:22 ` David Ahern
2013-12-04 10:11 ` Ingo Molnar
2013-12-04 12:57 ` Arnaldo Carvalho de Melo
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=1385995100.1710.11.camel@leonhard \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
/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.