[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1301665752.4859.678.camel@twins>
Date: Fri, 01 Apr 2011 15:49:12 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Lin Ming <ming.m.lin@...el.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
"2nddept-manager@....hitachi.co.jp"
<2nddept-manager@....hitachi.co.jp>
Subject: Re: [RFC PATCH] perf report: add sort by file lines
On Fri, 2011-04-01 at 21:22 +0800, Lin Ming wrote:
> On Fri, 2011-04-01 at 19:05 +0800, Peter Zijlstra wrote:
> > On Fri, 2011-04-01 at 19:44 +0900, Masami Hiramatsu wrote:
> > > E.g. an indirect jump makes it hard to find where it jumps to.
> >
> > Yes indirect jumps are 'interesting', is there anything in the debug
> > info that will help us out with the possible target sites?
> >
> > Also what generates indirect jumps, switch() stmts? Indirect function
> > call that get optimized might also be, but hopefully DWARF would tell us
> > about that and allow us to know the state right after the jump.
>
> I'm not sure.
>
> But I'm thinking another way to trace the register assignment by LBR
> records.
>
> LBR will introduce overhead, but it can tell us all the branches,
> including the indirect jump.
Yeah, but it would be nice to see how far we can get without using extra
information, we can always try and complement stuff later.
--
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