[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151021132440.GF10639@kernel.org>
Date: Wed, 21 Oct 2015 10:24:40 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Chandler Carruth <chandlerc@...il.com>,
Brendan Gregg <brendan.d.gregg@...il.com>,
Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Borislav Petkov <bp@...e.de>, David Ahern <dsahern@...il.com>,
Jiri Olsa <jolsa@...hat.com>,
Stephane Eranian <eranian@...gle.com>,
Wang Nan <wangnan0@...wei.com>,
Taeung Song <treeze.taeung@...il.com>
Subject: Re: [PATCH 13/16] perf callchain: Switch default to
'graph,0.5,caller'
Em Wed, Oct 21, 2015 at 10:21:36AM +0900, Namhyung Kim escreveu:
> On Tue, Oct 20, 2015 at 03:44:04PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Oct 20, 2015 at 07:21:16PM +0200, Frederic Weisbecker escreveu:
> > > On Tue, Oct 20, 2015 at 10:06:51AM -0300, Arnaldo Carvalho de Melo wrote:
> > And I noticed some other shortcoming of this ordering (caller) the stack
> > closer to userspace in a typical perf.data with callchains (perf record
> > -g) can have bogus addresses (-fomit-frame-pointer) :-\
> Maybe we need to add an option to ignore unresolved callchains?
We have:
-U, --hide-unresolved
Only display entries resolved to a symbol
But I think the problem here is different, its not about unresolved
stuff, its about invalid addresses, no?
- Arnaldo
--
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