aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/trace/Kconfig
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2009-09-14 11:58:24 -0400
committerSteven Rostedt <rostedt@goodmis.org>2009-09-14 11:58:24 -0400
commit1f5a6b45416694ff8c0d04625f1a438a0e380add (patch)
treebdf5a59ac8297ead4dd8fabea6124beb7d965cb4 /kernel/trace/Kconfig
parent20a58a77231c5f5f61470932503b889303e8d4f3 (diff)
tracing: make testing syscall events a separate configuration
Parag noticed that the number of event tests has increased tremendously: grep "Testing event" dmesg.31rc9 |wc -l 100 grep "Testing event" dmesg.31git |wc -l 1172 This is due to the testing of every syscall event when ftrace self test is enabled. This adds a bit more time to kernel boot up and can affect development by slowing down the time it takes between reboots. This option makes the testing of the syscall events into a separate config, to still be able to test most of ftrace internals at boot up but not have to wait for all the syscall events to be tested. The syscall event testing only tests the enabling and disabling of the trace point, since the syscalls are not executed. What really needs to be done is to somehow have a userspace tool test the syscall tracepoints as well. Reported-by: Parag Warudkar <parag.lkml@gmail.com> LKML-Reference: <f7848160909130815l3e768a30n3b28808bbe5c254b@mail.gmail.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/Kconfig')
-rw-r--r--kernel/trace/Kconfig12
1 files changed, 12 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 1ea0d1234f4a..aa002cef924c 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -469,6 +469,18 @@ config FTRACE_STARTUP_TEST
469 functioning properly. It will do tests on all the configured 469 functioning properly. It will do tests on all the configured
470 tracers of ftrace. 470 tracers of ftrace.
471 471
472config EVENT_TRACE_TEST_SYSCALLS
473 bool "Run selftest on syscall events"
474 depends on FTRACE_STARTUP_TEST
475 help
476 This option will also enable testing every syscall event.
477 It only enables the event and disables it and runs various loads
478 with the event enabled. This adds a bit more time for kernel boot
479 up since it runs this on every system call defined.
480
481 TBD - enable a way to actually call the syscalls as we test their
482 events
483
472config MMIOTRACE 484config MMIOTRACE
473 bool "Memory mapped IO tracing" 485 bool "Memory mapped IO tracing"
474 depends on HAVE_MMIOTRACE_SUPPORT && PCI 486 depends on HAVE_MMIOTRACE_SUPPORT && PCI