From: Tom Zanussi <tom.zanu...@linux.intel.com>
Add a testcase verifying basic tracing/error_log functionality.
Signed-off-by: Tom Zanussi <tom.zanu...@linux.intel.com>
Acked-by: Namhyung Kim <namhy...@kernel.org>
---
.../ftrace/test.d/ftrace/tracing-error-log.tc | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644
tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
b/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
new file mode 100644
index 000000000000..021c03fd885d
--- /dev/null
+++ b/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
@@ -0,0 +1,19 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0
+# description: ftrace - test tracing error log support
+
+fail() { #msg
+ echo $1
+ exit_fail
+}
+
+# event tracing is currently the only ftrace tracer that uses the
+# tracing error_log, hence this check
+if [ ! -f set_event ]; then
+ echo "event tracing is not supported"
+ exit_unsupported
+fi
+
+ftrace_errlog_check 'event filter parse error' '((sig >= 10 && sig < 15) ||
dsig ^== 17) && comm != bash' 'events/signal/signal_generate/filter'
+
+exit 0
--
2.14.1
