tracing: Use CONFIG_PREEMPTION
authorSebastian Andrzej Siewior <bigeasy@linutronix.de>
Tue, 15 Oct 2019 19:18:20 +0000 (21:18 +0200)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Wed, 13 Nov 2019 14:37:28 +0000 (09:37 -0500)
CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT.
Both PREEMPT and PREEMPT_RT require the same functionality which today
depends on CONFIG_PREEMPT.

Add additional header output for PREEMPT_RT.
Link: http://lkml.kernel.org/r/20191015191821.11479-34-bigeasy@linutronix.de
Cc: Ingo Molnar <mingo@redhat.com>
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Documentation/trace/ftrace-uses.rst
kernel/trace/trace.c

index 740bd02..2a05e77 100644 (file)
@@ -146,7 +146,7 @@ FTRACE_OPS_FL_RECURSION_SAFE
        itself or any nested functions that those functions call.
 
        If this flag is set, it is possible that the callback will also
-       be called with preemption enabled (when CONFIG_PREEMPT is set),
+       be called with preemption enabled (when CONFIG_PREEMPTION is set),
        but this is not guaranteed.
 
 FTRACE_OPS_FL_IPMODIFY
index f093a43..db7d06a 100644 (file)
@@ -3726,6 +3726,8 @@ print_trace_header(struct seq_file *m, struct trace_iterator *iter)
                   "desktop",
 #elif defined(CONFIG_PREEMPT)
                   "preempt",
+#elif defined(CONFIG_PREEMPT_RT)
+                  "preempt_rt",
 #else
                   "unknown",
 #endif