• Steven Rostedt's avatar
    tracing: make testing syscall events a separate configuration · 1f5a6b45
    Steven Rostedt authored
    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: default avatarParag Warudkar <parag.lkml@gmail.com>
    LKML-Reference: <f7848160909130815l3e768a30n3b28808bbe5c254b@mail.gmail.com>
    Signed-off-by: default avatarSteven Rostedt <rostedt@goodmis.org>
    1f5a6b45
trace_events.c 30.6 KB