linux-toradex.git/tools/testing/selftests/ftrace/test.d/event, branch master

selftests/ftrace: Test toplevel-enable for instance

2025-12-31T19:46:12+00:00

'available_events' is actually not required by
'test.d/event/toplevel-enable.tc' and its Existence has been tested in
'test.d/00basic/basic4.tc'.

So the require of 'available_events' can be dropped and then we can add
'instance' flag to test 'test.d/event/toplevel-enable.tc' for instance.

Test result show as below:
 # ./ftracetest test.d/event/toplevel-enable.tc
 === Ftrace unit tests ===
 [1] event tracing - enable/disable with top level files [PASS]
 [2] (instance)  event tracing - enable/disable with top level files [PASS]

 # of passed:  2
 # of failed:  0
 # of unresolved:  0
 # of untested:  0
 # of unsupported:  0
 # of xfailed:  0
 # of undefined(test bug):  0

Link: https://lore.kernel.org/r/20230509203659.1173917-1-zhengyejian1@huawei.com
Signed-off-by: Zheng Yejian 
Acked-by: Steven Rostedt (Google) 
Signed-off-by: Shuah Khan

selftests/tracing: Fix false failure of subsystem event test

2025-07-24T21:52:20+00:00

The subsystem event test enables all "sched" events and makes sure there's
at least 3 different events in the output. It used to cat the entire trace
file to | wc -l, but on slow machines, that could last a very long time.
To solve that, it was changed to just read the first 100 lines of the
trace file. This can cause false failures as some events repeat so often,
that the 100 lines that are examined could possibly be of only one event.

Instead, create an awk script that looks for 3 different events and will
exit out after it finds them. This will find the 3 events the test looks
for (eventually if it works), and still exit out after the test is
satisfied and not cause slower machines to run forever.

Link: https://lore.kernel.org/r/20250721134212.53c3e140@batman.local.home
Reported-by: Tengda Wu 
Closes: https://lore.kernel.org/all/20250710130134.591066-1-wutengda@huaweicloud.com/
Fixes: 1a4ea83a6e67 ("selftests/ftrace: Limit length in subsystem-enable tests")
Signed-off-by: Steven Rostedt (Google) 
Signed-off-by: Shuah Khan

selftests/ftrace: Add test that tests event :mod: commands

2025-01-16T14:41:50+00:00

Now that here's a :mod: command that can be sent into set_event, add a
test that tests its use. Both setting events for a loaded module, as well
as caching what events to set for a module that is not loaded yet.

Cc: Shuah Khan 
Cc: Masami Hiramatsu 
Cc: Mark Rutland 
Cc: Mathieu Desnoyers 
Cc: Andrew Morton 
Cc: linux-kselftest@vger.kernel.org
Link: https://lore.kernel.org/20250116143533.819228058@goodmis.org
Signed-off-by: Steven Rostedt (Google)

selftests/ftrace: Limit length in subsystem-enable tests

2024-04-04T16:29:10+00:00

While sched* events being traced and sched* events continuously happen,
"[xx] event tracing - enable/disable with subsystem level files" would
not stop as on some slower systems it seems to take forever.
Select the first 100 lines of output would be enough to judge whether
there are more than 3 types of sched events.

Fixes: 815b18ea66d6 ("ftracetest: Add basic event tracing test cases")
Cc: stable@vger.kernel.org
Signed-off-by: Yuanhe Shu 
Acked-by: Masami Hiramatsu (Google) 
Acked-by: Steven Rostedt (Google) 
Signed-off-by: Shuah Khan

selftests/ftrace: fix event-no-pid on 1-core machine

2021-06-24T00:29:26+00:00

When running event-no-pid test on small machines (e.g. cloud 1-core
instance), other events might not happen:

    + cat trace
    + cnt=0
    + [ 0 -eq 0 ]
    + fail No other events were recorded
    [15] event tracing - restricts events based on pid notrace filtering [FAIL]

Schedule a simple sleep task to be sure that some other process events
get recorded.

Fixes: ebed9628f5c2 ("selftests/ftrace: Add test to test new set_event_notrace_pid file")
Signed-off-by: Krzysztof Kozlowski 
Acked-by: Steven Rostedt (VMware) 
Signed-off-by: Shuah Khan

selftests/ftrace: Convert required interface checks into requires list

2020-06-16T16:39:20+00:00

Convert the required tracefs interface checking code with
requires: list.

Fixed merge conflicts in trigger-hist.tc and trigger-trace-marker-hist.tc
Shuah Khan 

Signed-off-by: Masami Hiramatsu 
Reviewed-by: Tom Zanussi 
Signed-off-by: Shuah Khan

selftests/ftrace: Add test to test new set_event_notrace_pid file

2020-03-27T20:39:02+00:00

A new file was added to the tracing directory that will allow a user to
place a PID into it and the task associated to that PID will not have its
events traced.  If the event-fork option is enabled, then neither will the
children of that task have its events traced.

Cc: linux-kselftest@vger.kernel.org
Cc: Shuah Khan 
Signed-off-by: Steven Rostedt (VMware)

selftests/ftrace: Add trace_printk sample module test

2018-10-24T20:49:36+00:00

Add trace_printk sample module test. This requires to
enable trace_printk.ko module for test.

Signed-off-by: Masami Hiramatsu 
Signed-off-by: Shuah Khan (Samsung OSG)

selftests/ftrace: Check set_event_pid result

2018-10-24T20:49:35+00:00

Ensure the set_event_pid shows set pid list.

Signed-off-by: Masami Hiramatsu 
Signed-off-by: Shuah Khan (Samsung OSG)

selftests/ftrace: Use loopback address instead of localhost

2018-10-24T20:49:35+00:00

Use raw loopback address instead of localhost, because
"localhost" can depend on nsswitch and in some case
we can not resolve the localhost.

Signed-off-by: Masami Hiramatsu 
Signed-off-by: Shuah Khan (Samsung OSG)