[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120308153130.GC7976@somewhere.redhat.com>
Date: Thu, 8 Mar 2012 16:31:34 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Arun Sharma <asharma@...com>, linux-kernel@...r.kernel.org,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>,
Namhyung Kim <namhyung.kim@....com>,
Tom Zanussi <tzanussi@...il.com>,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH 0/2] perf: add sort by inclusive time functionality (v2)
On Thu, Mar 08, 2012 at 08:29:01AM +0100, Ingo Molnar wrote:
>
> * Arun Sharma <asharma@...com> wrote:
>
> > This patch series refactors existing code a bit and adds sort by
> > inclusive time (time spent in the function + callees).
> >
> > Sample command lines:
> >
> > # perf record -ag -- sleep 1
> > # perf report -g graph,0.5,callee -n -s inclusive
>
> So I tried this out with:
>
> $ taskset 1 perf record -g git gc
>
> and got entries above 100% (in the TUI):
>
> $ perf report -g graph,0.5,callee -n -s inclusive
>
> + 321.11% 5628 [.] 0x392b609269
> + 142.27% 3774 [.] create_delta
> + 78.86% 1248 [.] lookup_object
> + 40.54% 1348 [k] system_call_fastpath
> [...]
>
> Is that expected?
I think this happens because of this:
- hists->stats.total_period += h->period;
+ if (!h->inclusive)
+ hists->stats.total_period += h->period;
Which I'm not sure why it is needed btw.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists