On Mon, Dec 16, 2013 at 07:18:52AM -0800, Andi Kleen wrote: > > So we could make the old ABI a CONFIG_PERF_EVENTS_COMPAT_X86_BTS kind > > of legacy option, turned off by default. That allows us its eventual > > future phasing out. > > > > It all depends on how useful the new tooling becomes: if interesting > > things can be done with it via an obvious, powerful interface then > > people might start using it. > > The thing to keep in mind is that BTS is really really slow. > > It's unlikely it'll be ever all that useful no matter how the API > looks like.
You're right it's extremely slow. But it can still be relevant for debugging, at least for apps that don't do too much CPU bound stuffs. My hope has always been that we can make a userspace function graph tracer out of its dumps. And I think we can, I'm pretty sure that would be a useful tool. Even better would be to allow for some perf timehist which we can use to navigate through the execution flow including all branches. But that's quite sophisticated (although possibly very useful), still a function graph would be a good beginning. Now if we find a faster replacement that can dump similar sources or even better if we can filter by branch type (call and ret is all we need for a function graph tracer) I'm all for it. But I agree with Ingo that some useful tooling should come along. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
