[PATCH 3/6] selftests/ftrace: Have reset_ftrace_filter handle modules

2018-02-09 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" If a function probe in set_ftrace_filter belongs to a module, it will contain the module name. Like: wmi_query_block [wmi]:traceoff:unlimited But writing: '!wmi_query_block [wmi]:traceoff' > set_ftrace_filter will cause an error. We

[PATCH 3/6] selftests/ftrace: Have reset_ftrace_filter handle modules

2018-02-09 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" If a function probe in set_ftrace_filter belongs to a module, it will contain the module name. Like: wmi_query_block [wmi]:traceoff:unlimited But writing: '!wmi_query_block [wmi]:traceoff' > set_ftrace_filter will cause an error. We still need to write:

[RFC][PATCH 3/6] selftests/ftrace: Have reset_ftrace_filter handle modules

2018-02-06 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" If a function probe in set_ftrace_filter belongs to a module, it will contain the module name. Like: wmi_query_block [wmi]:traceoff:unlimited But writing: '!wmi_query_block [wmi]:traceoff' > set_ftrace_filter will cause an error. We

[RFC][PATCH 3/6] selftests/ftrace: Have reset_ftrace_filter handle modules

2018-02-06 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" If a function probe in set_ftrace_filter belongs to a module, it will contain the module name. Like: wmi_query_block [wmi]:traceoff:unlimited But writing: '!wmi_query_block [wmi]:traceoff' > set_ftrace_filter will cause an error. We still need to write: