From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: tglx@linutronix.de, mhiramat@kernel.org, namhyung@kernel.org,
bigeasy@linutronix.de, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: [PATCH v5 09/11] selftests/ftrace: Add tracing/error_log testcase
Date: Sun, 31 Mar 2019 18:48:23 -0500 [thread overview]
Message-ID: <bf1c0d47a24672df945331462682d96296d1ab28.1554072478.git.tom.zanussi@linux.intel.com> (raw)
In-Reply-To: <cover.1554072478.git.tom.zanussi@linux.intel.com>
In-Reply-To: <cover.1554072478.git.tom.zanussi@linux.intel.com>
From: Tom Zanussi <tom.zanussi@linux.intel.com>
Add a testcase verifying basic tracing/error_log functionality.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Acked-by: Namhyung Kim <namhyung@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
next prev parent reply other threads:[~2019-03-31 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 23:48 [PATCH v5 00/11] tracing: common error_log for ftrace Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 01/11] tracing: Add tracing error log Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 02/11] tracing: Save the last hist command's associated event name Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 03/11] tracing: Use tracing error_log with hist triggers Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 04/11] tracing: Use tracing error_log with trace event filters Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 05/11] tracing: Use tracing error_log with probe events Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 06/11] selftests/ftrace: Add error_log testcase for probe errors Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 07/11] selftests/ftrace: Move kprobe/uprobe check_error() to test.d/functions Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 08/11] selftests/ftrace: Remove trigger-extended-error-support testcase Tom Zanussi
2019-03-31 23:48 ` Tom Zanussi [this message]
2019-03-31 23:48 ` [PATCH v5 10/11] tracing: Add tracing/error_log Documentation Tom Zanussi
2019-03-31 23:48 ` [PATCH v5 11/11] tracing: Add error_log to README Tom Zanussi
2019-04-01 2:19 ` [PATCH v5 00/11] tracing: common error_log for ftrace Masami Hiramatsu
2019-04-01 13:31 ` Tom Zanussi
2019-04-01 23:59 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf1c0d47a24672df945331462682d96296d1ab28.1554072478.git.tom.zanussi@linux.intel.com \
--to=zanussi@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®