tracing: Make a separate config for trace event self tests (b3015fe4) · Commits · 戴 / test

The trace event self tests enable loop through *all* events, enables each one, one at a time, runs some code to trigger various events (not necessarily the same events), and checks if anything went wrong. The issue is that trace events are usually the least likely start up test to cause a problem, but they take the longest to run (because there are so many events). When one of the other tests trigger a bug, the trace event start up tests causes the bisect to take much longer, because it takes 10s of seconds to get through the trace event tests. By making them a separate config (even though they are enabled by default if start up tests are set), it is possible to turn them off and still run the other tracing start up tests much quicker. Signed-off-by:

Steven Rostedt (VMware) <rostedt@goodmis.org>

kernel/trace/Kconfig

+11 −1

Original line number	Diff line number	Diff line
		@@ -596,9 +596,19 @@ config FTRACE_STARTUP_TEST
		functioning properly. It will do tests on all the configured
		tracers of ftrace.

		config EVENT_TRACE_STARTUP_TEST
		bool "Run selftest on trace events"
		depends on FTRACE_STARTUP_TEST
		default y
		help
		This option performs a test on all trace events in the system.
		It basically just enables each event and runs some code that
		will trigger events (not necessarily the event it enables)
		This may take some time run as there are a lot of events.

		config EVENT_TRACE_TEST_SYSCALLS
		bool "Run selftest on syscall events"
		depends on FTRACE_STARTUP_TEST
		depends on EVENT_TRACE_STARTUP_TEST
		help
		This option will also enable testing every syscall event.
		It only enables the event and disables it and runs various loads

kernel/trace/trace_events.c

+1 −1

Original line number	Diff line number	Diff line
		@@ -3190,7 +3190,7 @@ void __init trace_event_init(void)
		event_trace_enable();
		}

		#ifdef CONFIG_FTRACE_STARTUP_TEST
		#ifdef CONFIG_EVENT_TRACE_STARTUP_TEST

		static DEFINE_SPINLOCK(test_spinlock);
		static DEFINE_SPINLOCK(test_spinlock_irq);

Admin message