From: Steven Rostedt <rostedt@goodmis.org>
To: fuyufan <835863489@qq.com>
Cc: mhiramat@kernel.org, mingo@redhat.com, zanussi@kernel.org,
linux-kernel@vger.kernel.org, xuhuijie <xuhujie2@huawei.com>,
xuhuijie <xuhujie2@gmail.com>
Subject: Re: [RFC][PATCH v5 3/4] trace/objtrace: Add testcases for objtrace trigger parsing
Date: Wed, 5 Jan 2022 19:53:27 -0500 [thread overview]
Message-ID: <20220105195327.5eac3a45@rorschach.local.home> (raw)
In-Reply-To: <tencent_CA3FD88F43A620435A6D24163EDD41AD7B07@qq.com>
On Thu, 6 Jan 2022 00:02:53 +0000
fuyufan <835863489@qq.com> wrote:
> From: xuhuijie <xuhujie2@huawei.com>
Needs a change log.
-- Steve
>
> Signed-off-by: xuhuijie <xuhujie2@huawei.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
next parent reply other threads:[~2022-01-06 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211113120632.94754-1-xuhujie2@gmail.com>
[not found] ` <tencent_CA3FD88F43A620435A6D24163EDD41AD7B07@qq.com>
2022-01-06 0:53 ` Steven Rostedt [this message]
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 3/4] trace/objtrace: Add testcases for objtrace trigger parsing Jeff Xie
2021-11-19 14:09 ` Masami Hiramatsu
2021-11-21 17:16 ` Jeff Xie
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=20220105195327.5eac3a45@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=835863489@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=xuhujie2@gmail.com \
--cc=xuhujie2@huawei.com \
--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
Powered by JetHome