From: Jeff Xie <xiehuan09@gmail.com>
To: rostedt@goodmis.org
Cc: mhiramat@kernel.org, mingo@redhat.com, zanussi@kernel.org,
linux-kernel@vger.kernel.org, Jeff Xie <xiehuan09@gmail.com>
Subject: [RFC][PATCH v5 3/4] trace/objtrace: Add testcases for objtrace trigger parsing
Date: Sat, 13 Nov 2021 20:06:31 +0800 [thread overview]
Message-ID: <20211113120632.94754-3-xiehuan09@gmail.com> (raw)
In-Reply-To: <20211113120632.94754-1-xiehuan09@gmail.com>
Signed-off-by: Jeff Xie <xiehuan09@gmail.com>
---
.../ftrace/test.d/trigger/trigger-objtrace.tc | 41 +++++++++++++++++++
1 file changed, 41 insertions(+)
create mode 100644 tools/testing/selftests/ftrace/test.d/trigger/trigger-objtrace.tc
diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-objtrace.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-objtrace.tc
new file mode 100644
index 000000000000..4efcd7eee694
--- /dev/null
+++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-objtrace.tc
@@ -0,0 +1,41 @@
+#!/bin/sh
+# SPDX-License-Identifier: GPL-2.0
+# description: event trigger - test objtrace-trigger
+# requires: kprobe_events
+
+fail() { #msg
+ echo $1
+ exit_fail
+}
+
+echo 'p bio_add_page arg1=$arg1' > kprobe_events
+
+FEATURE=`grep objtrace events/kprobes/p_bio_add_page_0/trigger`
+if [ -z "$FEATURE" ]; then
+ echo "objtrace trigger is not supported"
+ exit_unsupported
+fi
+
+echo "Test objtrace trigger"
+echo 'objtrace:add:0x28(arg1):u32:1 if comm == "cat"' > \
+ events/kprobes/p_bio_add_page_0/trigger
+if [ -z $? ]; then
+ fail "objtrace trigger syntax error"
+fi
+
+echo "Test objtrace semantic errors"
+
+# Being lack of type size
+! echo 'objtrace:add:0x28(arg1):1' > events/kprobes/p_bio_add_page_0/trigger
+# Being lack of objtrace command
+! echo 'objtrace:0x28(arg1):u32:1' > events/kprobes/p_bio_add_page_0/trigger
+# Bad parameter name
+! echo 'objtrace:add:argx:u32:1' > events/kprobes/p_bio_add_page_0/trigger
+
+echo "reset objtrace trigger"
+
+echo '!objtrace:add:0x28(arg1):u32' > \
+ events/kprobes/p_bio_add_page_0/trigger
+echo '-:p_bio_add_page_0' >> ./kprobe_events
+
+exit 0
--
2.25.1
next prev parent reply other threads:[~2021-11-13 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 12:06 [RFC][PATCH v5 1/4] trace: Add trace any kernel object Jeff Xie
2021-11-13 12:06 ` [RFC][PATCH v5 2/4] trace/objtrace: get the value of the object Jeff Xie
2021-11-19 14:01 ` Masami Hiramatsu
2021-11-21 17:15 ` Jeff Xie
2021-11-26 13:47 ` Jeff Xie
2021-11-26 15:19 ` Masami Hiramatsu
2021-11-26 15:32 ` Jeff Xie
2021-11-13 12:06 ` Jeff Xie [this message]
2021-11-19 14:09 ` [RFC][PATCH v5 3/4] trace/objtrace: Add testcases for objtrace trigger parsing Masami Hiramatsu
2021-11-21 17:16 ` Jeff Xie
2021-11-13 12:06 ` [RFC][PATCH v5 4/4] trace/objtrace: Add documentation for objtrace trigger Jeff Xie
2021-11-19 14:00 ` [RFC][PATCH v5 1/4] trace: Add trace any kernel object Masami Hiramatsu
2021-11-19 14:58 ` Jeff Xie
2021-11-21 17:13 ` Jeff Xie
[not found] <20211113120632.94754-1-xuhujie2@gmail.com>
[not found] ` <tencent_CA3FD88F43A620435A6D24163EDD41AD7B07@qq.com>
2022-01-06 0:53 ` [RFC][PATCH v5 3/4] trace/objtrace: Add testcases for objtrace trigger parsing Steven Rostedt
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=20211113120632.94754-3-xiehuan09@gmail.com \
--to=xiehuan09@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=zanussi@kernel.org \
/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