On Mon, Oct 28, 2013 at 06:09:30PM +0900, Namhyung Kim wrote: > On Mon, 28 Oct 2013 08:42:44 +0000, Rodrigo Campos wrote: > > On Mon, Oct 28, 2013 at 02:09:49PM +0900, Namhyung Kim wrote: > >> Anyway, You can find the series and discussion on the link below: > >> > >> https://lkml.org/lkml/2012/9/13/81 > > > > I've read the cover letter for that series and probably because I don't know > > about perf internals I have a question: How will "--culumate" interact with > > "--sort=dso" for example ? > > > > I mean, is it possible for that to show more than 100% ? (if you add all the > > 93.35% in your example in the cover letter, or something similar). Or > > "--culumate --sort=dso" will just group together all entries that have a > > dso in > > the call chain ? > > Hmm.. I think --cumulate option is only meaningful when sort order > includes symbol. Maybe I can add support for --sort=dso case as well > but not sure it's worth. Do you think it's really needed?
I don't know if it is *needed*, but that was what I need :) I mean, what I was looking for is a way to know the percentage spent when some symbol in the call chain belongs to a DSO. Like group all samples that have a symbol of a DSO in the callchain, and know the percentage for that group. Something like the "inclusive" time spent inside a library. > > Sorry if the question was too obvious if I knew about perf internals :S > > No need to sorry about it. :) Thanks =) Thanks again, Rodrigo -- 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/
