tracing: Fixup logic inversion on setting trace_global_clock defaults
authorChris Wilson <chris@chris-wilson.co.uk>
Wed, 4 Apr 2018 21:24:50 +0000 (22:24 +0100)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Fri, 6 Apr 2018 12:56:53 +0000 (08:56 -0400)
commit5125eee4e698f02b8e1a364ad5d7560f908d855f
tree2310e1882a7603e2a96a8bec286052ce8d9e9fb3
parentf7a1570da91558fb85b61e53243fe3fa79e2bbae
tracing: Fixup logic inversion on setting trace_global_clock defaults

In commit 932066a15335 ("tracing: Default to using trace_global_clock if
sched_clock is unstable"), the logic for deciding to override the
default clock if unstable was reversed from the earlier posting. I was
trying to reduce the width of the message by using an early return
rather than a if-block, but reverted back to using the if-block and
accidentally left the predicate inverted.

Link: http://lkml.kernel.org/r/20180404212450.26646-1-chris@chris-wilson.co.uk
Fixes: 932066a15335 ("tracing: Default to using trace_global_clock if sched_clock is unstable")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
kernel/trace/trace.c