From: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
To: Akanksha J N <akanksha@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Cc: mhiramat@kernel.org, rostedt@goodmis.org, shuah@kernel.org
Subject: Re: [PATCH v2 0/2] selftests/ftrace: Add tests for kprobes and optimized probes
Date: Mon, 24 Apr 2023 16:39:56 +0530 [thread overview]
Message-ID: <1682334408.u49nhd1gk9.naveen@linux.ibm.com> (raw)
In-Reply-To: <20230418095557.19061-1-akanksha@linux.ibm.com>
Akanksha J N wrote:
> This patchset adds a stress test for kprobes and a test for checking
> optimized probes.
> The two tests are being added based on the below discussion:
> https://lore.kernel.org/all/20230128101622.ce6f8e64d929e29d36b08b73@kernel.org/
>
> Changelog:
>
>
> * Add an explicit fork after enabling the events ( echo "forked" )
> * Remove the extended test from multiple_kprobe_types.tc which adds
> multiple consecutive probes in a function and add it as a
> separate test case.
> * Add new test case which checks for optimized probes.
>
> Akanksha J N (2):
> selftests/ftrace: Add new test case which adds multiple consecutive
> probes in a function
> selftests/ftrace: Add new test case which checks for optimized probes
>
> .../test.d/kprobe/kprobe_insn_boundary.tc | 19 +++++++++++
> .../ftrace/test.d/kprobe/kprobe_opt_types.tc | 34 +++++++++++++++++++
> 2 files changed, 53 insertions(+)
> create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_insn_boundary.tc
> create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_opt_types.tc
This series looks good to me.
Acked-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
- Naveen
prev parent reply other threads:[~2023-04-24 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 9:55 [PATCH v2 0/2] selftests/ftrace: Add tests for kprobes and optimized probes Akanksha J N
2023-04-18 9:55 ` [PATCH v2 1/2] selftests/ftrace: Add new test case which adds multiple consecutive probes in a function Akanksha J N
2023-04-25 0:12 ` Masami Hiramatsu
2023-04-18 9:55 ` [PATCH v2 2/2] selftests/ftrace: Add new test case which checks for optimized probes Akanksha J N
2023-04-25 0:10 ` Masami Hiramatsu
2023-04-25 5:28 ` Naveen N. Rao
2023-04-25 14:41 ` Masami Hiramatsu
2023-04-26 11:01 ` Naveen N. Rao
2023-04-24 11:09 ` Naveen N. Rao [this message]
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=1682334408.u49nhd1gk9.naveen@linux.ibm.com \
--to=naveen.n.rao@linux.ibm.com \
--cc=akanksha@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).