On Tue, Feb 11, 2014 at 12:31:49PM +0100, Peter Zijlstra wrote: > On Tue, Feb 11, 2014 at 12:28:47PM +0100, Stephane Eranian wrote: > > On Tue, Feb 11, 2014 at 12:14 PM, Peter Zijlstra <[email protected]> > > wrote: > > > On Tue, Feb 11, 2014 at 12:08:56PM +0100, Stephane Eranian wrote: > > >> Assuming you can decode and get the info about the base registers used, > > >> you'd have to do this for each arch with load/store sampling > > >> capabilities. > > >> this is painful compared to getting the portable info from dwarf > > >> directly. > > > > > > But its useful now, as compared to whenever GCC gets around to > > > implementing more dwarves and that GCC getting used widely enough to > > > actually rely on it. > > > > > > All you need for the decode is a disassembler, and every arch should > > > already have multiple of those. Should be easy to reuse one, right? > > > > I know, and you want to pull this into the perf tool? > > Sure why not, its already got the world and then some :/ > > It would be just another dynamic lib.
The added benefit is that we could get rid of the objdump usage for annotate if we find a usable disasm lib. At which point we can start improving the annotations with these variable/type information as well. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
