From: Shuah Khan <skhan@linuxfoundation.org>
To: Jeff Xie <xiehuan09@gmail.com>, rostedt@goodmis.org
Cc: mingo@redhat.com, mhiramat@kernel.org, zanussi@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, linux-doc@vger.kernel.org, corbet@lwn.net,
chensong_2000@189.cn, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v13 3/4] selftests/ftrace: Add testcases for objtrace
Date: Fri, 8 Jul 2022 10:26:46 -0600 [thread overview]
Message-ID: <db539a80-8cad-b5bf-3bea-6a883f48585e@linuxfoundation.org> (raw)
In-Reply-To: <20220626025604.277413-4-xiehuan09@gmail.com>
On 6/25/22 8:56 PM, Jeff Xie wrote:
> Add a series of testcases to illustrate correct and incorrect usage of
> objtrace trigger.
>
> Signed-off-by: Jeff Xie <xiehuan09@gmail.com>
> Tested-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> .../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
>
Assuming this patch depends on the other kernel/trace changes in this
series, here is my Ack for this series to go through tracing tree
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2022-07-08 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 2:56 [PATCH v13 0/4] trace: Introduce objtrace trigger to trace the kernel object Jeff Xie
2022-06-26 2:56 ` [PATCH v13 1/4] trace: Add trace any " Jeff Xie
2022-06-26 2:56 ` [PATCH v13 2/4] trace/objtrace: Get the value of the object Jeff Xie
2022-06-26 15:13 ` Masami Hiramatsu
2022-06-26 2:56 ` [PATCH v13 3/4] selftests/ftrace: Add testcases for objtrace Jeff Xie
2022-07-08 16:26 ` Shuah Khan [this message]
2022-06-26 2:56 ` [PATCH v13 4/4] Documentation: trace/objtrace: Add documentation " Jeff Xie
2022-06-27 2:14 ` Bagas Sanjaya
2022-06-27 7:45 ` Jeff Xie
2022-06-28 1:37 ` Jeff Xie
2022-06-28 2:31 ` Bagas Sanjaya
2022-06-28 2:48 ` 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=db539a80-8cad-b5bf-3bea-6a883f48585e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=chensong_2000@189.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=xiehuan09@gmail.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