summaryrefslogtreecommitdiffstats
path: root/block/bounce.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2018-08-09 03:28:05 +0200
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2018-08-10 21:12:00 +0200
commit3f1756dc210e5abb37121da3e7c10d65920f6ec0 (patch)
tree9adb16d03c5e6f1de6d1fc765da1d5aa0590e78e /block/bounce.c
parenttracing/irqsoff: Handle preempt_count for different configs (diff)
downloadlinux-3f1756dc210e5abb37121da3e7c10d65920f6ec0.tar.xz
linux-3f1756dc210e5abb37121da3e7c10d65920f6ec0.zip
tracing: More reverting of "tracing: Centralize preemptirq tracepoints and unify their usage"
Joel Fernandes created a nice patch that cleaned up the duplicate hooks used by lockdep and irqsoff latency tracer. It made both use tracepoints. But the latency tracer is triggering warnings when using tracepoints to call into the latency tracer's routines. Mainly, they can be called from NMI context. If that happens, then the SRCU may not work properly because on some architectures, SRCU is not safe to be called in both NMI and non-NMI context. This is a partial revert of the clean up patch c3bc8fd637a9 ("tracing: Centralize preemptirq tracepoints and unify their usage") that adds back the direct calls into the latency tracer. It also only calls the trace events when not in NMI. Link: http://lkml.kernel.org/r/20180809210654.622445925@goodmis.org Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org> Fixes: c3bc8fd637a9 ("tracing: Centralize preemptirq tracepoints and unify their usage") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'block/bounce.c')
0 files changed, 0 insertions, 0 deletions