selftest/ftrace: Fix function trigger test to handle trace not disabling the tracer
authorSteven Rostedt (VMware) <rostedt@goodmis.org>
Wed, 18 Mar 2020 15:13:45 +0000 (11:13 -0400)
committerSteven Rostedt (VMware) <rostedt@goodmis.org>
Thu, 19 Mar 2020 20:31:22 +0000 (16:31 -0400)
commit8c77f0ba41566b5a54a49c53107cc855d89ff4c1
tree674f6ce702e0f13b1a32c87ffdf2d0f865a3f90b
parentbf2cbe044da275021b2de5917240411a19e5c50d
selftest/ftrace: Fix function trigger test to handle trace not disabling the tracer

The ftrace selftest "ftrace - test for function traceon/off triggers"
enables all events and reads the trace file. Now that the trace file does
not disable tracing, and will attempt to continually read new data that is
added, the selftest gets stuck reading the trace file. This is because the
data added to the trace file will fill up quicker than the reading of it.

By only enabling scheduling events, the read can keep up with the writes.
Instead of enabling all events, only enable the scheduler events.

Link: http://lkml.kernel.org/r/20200318111345.0516642e@gandalf.local.home
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
tools/testing/selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc