Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-11-01 Thread Rodrigo Campos
On Fri, Nov 01, 2013 at 04:07:22PM +0900, Namhyung Kim wrote: > Hi Rodrigo, > > On Thu, 31 Oct 2013 11:13:34 +, Rodrigo Campos wrote: > > On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: > > I think the right fix is assigning "iter->priv = NULL" as you said. But > I changed this

Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-11-01 Thread Rodrigo Campos
On Fri, Nov 01, 2013 at 04:07:22PM +0900, Namhyung Kim wrote: > Hi Rodrigo, > > On Thu, 31 Oct 2013 11:13:34 +, Rodrigo Campos wrote: > > On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: > >> @@ -538,6 +586,7 @@ iter_finish_cumulative_entry(struct add_entry_iter > >> *iter, > >>

Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-11-01 Thread Jiri Olsa
On Fri, Nov 01, 2013 at 01:29:42PM +0100, Jiri Olsa wrote: > On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: > > SNIP > > > * double accounting. > > @@ -501,8 +528,29 @@ iter_add_next_cumulative_entry(struct add_entry_iter > > *iter, > > { > > struct perf_evsel *evsel = i

Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-11-01 Thread Jiri Olsa
On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: SNIP >* double accounting. > @@ -501,8 +528,29 @@ iter_add_next_cumulative_entry(struct add_entry_iter > *iter, > { > struct perf_evsel *evsel = iter->evsel; > struct perf_sample *sample = iter->sample; > + st

Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-11-01 Thread Namhyung Kim
Hi Rodrigo, On Thu, 31 Oct 2013 11:13:34 +, Rodrigo Campos wrote: > On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: >> From: Namhyung Kim >> /* >> + * This is for detecting cycles or recursions so that they're >> + * cumulated only one time to prevent entries more t

Re: [PATCH 08/14] perf report: Cache cumulative callchains

2013-10-31 Thread Rodrigo Campos
On Thu, Oct 31, 2013 at 03:56:10PM +0900, Namhyung Kim wrote: > From: Namhyung Kim > > It is possble that a callchain has cycles or recursive calls. In that > case it'll end up having entries more than 100% overhead in the > output. In order to prevent such entries, cache each callchain node >

[PATCH 08/14] perf report: Cache cumulative callchains

2013-10-30 Thread Namhyung Kim
From: Namhyung Kim It is possble that a callchain has cycles or recursive calls. In that case it'll end up having entries more than 100% overhead in the output. In order to prevent such entries, cache each callchain node and skip if same entry already cumulated. Cc: Arun Sharma Cc: Frederic W