Messages in this thread Patch in this message | | | From | Adrian Hunter <> | Subject | [PATCH 03/19] perf report: Set perf time interval in itrace_synth_ops | Date | Tue, 4 Jun 2019 16:00:01 +0300 |
| |
Instruction trace decoders can optimize output based on what time intervals will be filtered, so pass that information in itrace_synth_ops.
Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> --- tools/perf/builtin-report.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/perf/builtin-report.c b/tools/perf/builtin-report.c index 1ca533f06a4c..91c40808380d 100644 --- a/tools/perf/builtin-report.c +++ b/tools/perf/builtin-report.c @@ -1428,6 +1428,10 @@ int cmd_report(int argc, const char **argv) &report.range_num); if (ret < 0) goto error; + + itrace_synth_opts__set_time_range(&itrace_synth_opts, + report.ptime_range, + report.range_num); } if (session->tevent.pevent && @@ -1449,8 +1453,10 @@ int cmd_report(int argc, const char **argv) ret = 0; error: - if (report.ptime_range) + if (report.ptime_range) { + itrace_synth_opts__clear_time_range(&itrace_synth_opts); zfree(&report.ptime_range); + } zstd_fini(&(session->zstd_data)); perf_session__delete(session); return ret; -- 2.17.1
| |