History log of /linux-master/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-hist.tc
Revision Date Author Comments
# 3591e90f 02-Jun-2020 Masami Hiramatsu <mhiramat@kernel.org>

selftests/ftrace: Convert required interface checks into requires list

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 <skhan@linuxfoundation.org>

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>


# 43708c0a 09-Jun-2020 Flavio Suligoi <f.suligoi@asem.it>

tools: testing: ftrace: trigger: fix spelling mistake

Fix typo: "tigger" --> "trigger"

Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>


# e527c470 30-Aug-2018 Masami Hiramatsu <mhiramat@kernel.org>

selftests/ftrace: Remove unneeded per-test init/cleanup ftrace

Since ftracetest framework calls initialize_ftrace() right before
each test and after all tests, we don't need to init/cleanup
ftrace for each test case.
Just remove such unneeded init/cleanup code because it can
increase logfile size.

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Shuah Khan (Samsung OSG) <shuah@kernel.org>


# c349d4af 14-May-2018 Steven Rostedt (VMware) <rostedt@goodmis.org>

tracing/selftest: Add selftests to test trace_marker histogram triggers

Add a couple of tests that test the trace_marker histogram triggers.
One does a straight histogram test, the other will create a synthetic event
and test the latency between two different writes (using filters to
differentiate between them).

Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>