On Mon, Jul 08, 2013 at 07:57:46AM -0400, Greg Price wrote: > On Sun, Jul 07, 2013 at 03:13:40PM +0200, Jiri Olsa wrote: > > On Mon, Jul 01, 2013 at 10:28:45AM -0400, Greg Price wrote: > > > For example, in an application with an expensive function > > > implemented with deeply nested recursive calls, the default > > > call-graph presentation is dominated by the different callchains > > > within that function. By ignoring these callees, we can collect > > > the callchains leading into the function and compactly identify > > > what to blame for expensive calls. > > > > hi, > > what's this one based on? I cannot get it applied on acme's perf/core > > That was on v3.10. Here it is on 6d895ece5, which is currently acme's > perf/core. > > Cheers, > Greg > > > -- >8 -- > Date: Thu, 6 Dec 2012 21:48:05 -0800 > > For example, in an application with an expensive function > implemented with deeply nested recursive calls, the default > call-graph presentation is dominated by the different callchains > within that function. By ignoring these callees, we can collect > the callchains leading into the function and compactly identify > what to blame for expensive calls.
change looks ok, but I'm not that confident in this part, so at least: Tested-by: Jiri Olsa <jo...@redhat.com> thanks, jirka -- 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/