On Thu, 2012-09-13 at 16:19 +0900, Namhyung Kim wrote: > When --cumulate option is given, it'll be shown like this: > > $ perf report --cumulate > (...) > + 93.63% abc libc-2.15.so [.] __libc_start_main > + 93.35% abc abc [.] main > + 93.35% abc abc [.] c > + 93.35% abc abc [.] b > + 93.35% abc abc [.] a > + 5.17% abc ld-2.15.so [.] _dl_map_object > + 5.17% abc ld-2.15.so [.] _dl_map_object_from_fd > + 1.13% abc ld-2.15.so [.] _dl_start_user > + 1.13% abc ld-2.15.so [.] _dl_start > + 0.29% abc perf [.] main > + 0.29% abc perf [.] run_builtin > + 0.29% abc perf [.] cmd_record > + 0.29% abc libpthread-2.15.so [.] __libc_close > + 0.07% abc ld-2.15.so [.] _start > + 0.07% abc [kernel.kallsyms] [k] page_fault > > (This output came from TUI since stdio bothered by callchains)
Right, so I tried this and I would expect the callchains to be inverted too, so that when I expand say 'c' I would see that 'c' calls 'b' for 100% which calls 'a' for 100%. Instead I get the regular callchains, expanding 'c' gives me main calls it for 100%. Adding -G (invert callchains) doesn't make it better, in that case, when I expand 'c' we start at '__libc_start_main' instead of 'c'. Is there anything I'm missing? -- 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/
