[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160119210725.GI27085@kernel.org>
Date: Tue, 19 Jan 2016 18:07:25 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Jiri Olsa <jolsa@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Stephane Eranian <eranian@...gle.com>,
Wang Nan <wangnan0@...wei.com>,
Don Zickus <dzickus@...hat.com>,
Pekka Enberg <penberg@...nel.org>,
Moinuddin Quadri <moin18@...il.com>
Subject: Re: [RFC/PATCHSET 00/17] perf tools: Add support for hierachy view
(v2)
Em Tue, Jan 19, 2016 at 06:03:39PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Jan 19, 2016 at 07:45:06PM +0900, Namhyung Kim escreveu:
> > On Sun, Jan 17, 2016 at 08:31:53PM +0100, Andi Kleen wrote:
> > > Now we only need a better percent-limit that handles all
> > > leaves correctly...
> > Hmm.. could you tell me where the percent-limit doesn't work
> > correctly?
> Yeah, please elaborate, I'm testing:
> perf top -s comm,dso,sym --hierarchy --percent-limit 0.5
>
> And it seems to work...
For instance, running that top command above, then expanding some of the
callchains and pressing 'P' to generate a perf.hist.0 output file, all
obey the 0.5 threshold for discading entries with less than that
percentage, what is the problem you're noticing? Is it only in stdio or
what?
- 76.76% cc1
- 62.43% cc1
2.82% [.] _cpp_lex_token
1.59% [.] ht_lookup_with_hash
1.23% [.] ggc_internal_alloc
0.85% [.] bitmap_set_bit
0.53% [.] cpp_get_token_with_location
0.51% [.] ht_lookup
- 7.77% libc-2.22.so
2.06% [.] _int_malloc
0.84% [.] _int_free
0.57% [.] _IO_putc
0.55% [.] malloc_consolidate
- 5.86% [kernel]
- 9.38% as
+ 6.03% as
+ 1.39% [kernel]
+ 1.28% libc-2.22.so
- 3.41% gcc
+ 1.63% [kernel]
+ 0.64% [unknown]
- 0.52% ccache
+ 2.28% ld
+ 1.85% perf
+ 1.45% sh
+ 1.16% perl
+ 0.55% make
Powered by blists - more mailing lists