Commit 913ea4d0 authored Mar 30, 2018 by Chris Wilson Committed by Steven Rostedt (VMware) Apr 06, 2018

tracing: Mention trace_clock=global when warning about unstable clocks

Mention the alternative of adding trace_clock=global to the kernel
command line when we detect that we've used an unstable clock across a
suspend/resume cycle.

Link: http://lkml.kernel.org/r/20180330150132.16903-2-chris@chris-wilson.co.uk



Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

parent 3fd49c9e

kernel/trace/ring_buffer.c

+2 −1

Original line number	Diff line number	Diff line
		@@ -2731,7 +2731,8 @@ rb_handle_timestamp(struct ring_buffer_per_cpu *cpu_buffer,
		sched_clock_stable() ? "" :
		"If you just came from a suspend/resume,\n"
		"please switch to the trace global clock:\n"
		" echo global > /sys/kernel/debug/tracing/trace_clock\n");
		" echo global > /sys/kernel/debug/tracing/trace_clock\n"
		"or add trace_clock=global to the kernel command line\n");
		info->add_timestamp = 1;
		}