diff options
| author |   Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-11-08 12:19:14 -0500 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-11-13 09:36:49 -0500 |
| commit | 646f01ccdd59f989f0a1866d2b3503e1855358d8 (patch) | |
| tree | 43ff72733bc74a70358ca823462f8979e13ed1b4 /CREDITS | |
| parent | ftrace: Add sample module that uses register_ftrace_direct() (diff) | |
| download | wireguard-linux-646f01ccdd59f989f0a1866d2b3503e1855358d8.tar.xz wireguard-linux-646f01ccdd59f989f0a1866d2b3503e1855358d8.zip | |
ftrace/selftest: Add tests to test register_ftrace_direct()
Add two test cases that test the new ftrace direct functionality if the
ftrace-direct sample module is available. One test case tests against each
available tracer (function, function_graph, mmiotrace, etc), and the other
test tests against a kprobe at the same location as the direct caller. Both
tests follow the same pattern of testing combinations:
enable test (either the tracer or the kprobe)
load direct function module
unload direct function module
disable test
enable test
load direct function module
disable test
unload direct function module
load direct function module
enable test
disable test
unload direct function module
load direct function module
enable test
unload direct function module
disable test
As most the bugs in development happened with various ways of enabling or
disabling the direct calls with function tracer in one of these
combinations.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions