On Fri, Mar 11, 2011 at 12:57:01PM +0100, Frederic Weisbecker wrote: > On Thu, Mar 10, 2011 at 10:32:43PM +0800, Sam Liao wrote: > > the sysprof that Ingo mentioned. > > sysprof does something like that? > > Note, another reason to avoid abusing the event.ip to group > per caller, is that we could be able to: > > perf report -s caller,sym -g caller > > If we limit callchains to start from a given foo.so, this may > sort hists per caller and then per endpoint. > > If your library offers function func1, func2, etc... It will sort > them per usage (func1 has been first used, then func2, etc...)
I meant func1 has been the most used, then came func2, etc... > then per endpoint overhead (func1 most often sticks in strcpy(), > then on read(), etc....). > > Right? > > That may or may not be useful. I don't know. In fact I don't > want to take the responsibility to judge whether it's useful > or not. Thus I prefer caller and ip to be two different > properties of hist entries and not having one absusing the > other, so that we don't prevent this feature to exist (or many > other sort combinations I haven't imagined). -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
