On Thu, Oct 02, 2014 at 12:12:14PM +0900, Namhyung Kim wrote: > Normally the callchain_param.record_mode is used only for record path. > But as it might need to prepare something for dwarf unwinding, setup > this info for perf report too. > > Cc: Jiri Olsa <[email protected]> > Cc: David Ahern <[email protected]> > Cc: Jean Pihet <[email protected]> > Cc: Frederic Weisbecker <[email protected]> > Signed-off-by: Namhyung Kim <[email protected]> > --- > tools/perf/builtin-report.c | 6 ++++++ > tools/perf/tests/dwarf-unwind.c | 3 +++ > tools/perf/util/callchain.h | 2 ++ > tools/perf/util/hist.h | 2 -- > 4 files changed, 11 insertions(+), 2 deletions(-) > > diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c > index ac145fae0521..495168e73d4a 100644 > --- a/tools/perf/builtin-report.c > +++ b/tools/perf/builtin-report.c > @@ -257,6 +257,12 @@ static int report__setup_sample_type(struct report *rep) > } > } > > + if (symbol_conf.use_callchain || symbol_conf.cumulate_callchain) { > + if (sample_type & PERF_SAMPLE_REGS_USER)
should we check also for PERF_SAMPLE_STACK_USER? as in machine__resolve_callchain thanks, jirka -- 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/
