From fa2785989cc13b49eec8d46bdad399730587ce1d Mon Sep 17 00:00:00 2001 From: Neeraj Upadhyay Date: Mon, 30 Nov 2020 12:21:15 +0530 Subject: [PATCH] trace: Do not use latency format for ftrace minidump Minidump ftrace need absolute timestamp of an event, and not the relative timestamp from buffer start time. So, do not use latency format for them. Change-Id: I5ed1aaac62a16e312d8c1d2f3fcbfc2781c4af77 Signed-off-by: Neeraj Upadhyay --- kernel/trace/trace.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c index 7f754e0109da..435ae2cf5068 100644 --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -9085,7 +9085,9 @@ void ftrace_dump(enum ftrace_dump_mode oops_dump_mode) cnt++; trace_iterator_reset(&iter); - iter.iter_flags |= TRACE_FILE_LAT_FMT; + /* Minidump ftraces need absolute event timestamp */ + if (!IS_ENABLED(CONFIG_QCOM_MINIDUMP_FTRACE)) + iter.iter_flags |= TRACE_FILE_LAT_FMT; if (trace_find_next_entry_inc(&iter) != NULL) { int ret;