From: Shuah Khan <skhan@linuxfoundation.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Akanksha J N <akanksha@linux.ibm.com>
Cc: linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, shuah@kernel.org,
naveen.n.rao@linux.ibm.com,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 2/2] selftests/ftrace: Add new test case which checks for optimized probes
Date: Mon, 8 May 2023 11:36:28 -0600 [thread overview]
Message-ID: <54bec864-5e4f-8432-a331-e4ea5fc2ba31@linuxfoundation.org> (raw)
In-Reply-To: <20230430105231.2e7f5bd8a3f879d2330485d2@kernel.org>
On 4/29/23 19:52, Masami Hiramatsu (Google) wrote:
> On Fri, 28 Apr 2023 22:08:42 +0530
> Akanksha J N <akanksha@linux.ibm.com> wrote:
>
>> Add new test case kprobe_opt_types.tc which enables and checks
>> if each probe has been optimized in order to test potential issues with
>> optimized probes.
>> The '|| continue' is added with the echo statement to ignore errors that
>> are caused by trying to add kprobes to non probeable lines and continue
>> with the test.
>>
>> Signed-off-by: Akanksha J N <akanksha@linux.ibm.com>
>
> Thanks! This looks good to me.
>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
Would you like this patch to go through kselftest tree?
If not here is my Ack:
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2023-05-08 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 16:38 [PATCH v3 0/2] selftests/ftrace: Add tests for kprobes and optimized probes Akanksha J N
2023-04-28 16:38 ` [PATCH v3 1/2] selftests/ftrace: Add new test case which adds multiple consecutive probes in a function Akanksha J N
2023-04-28 16:38 ` [PATCH v3 2/2] selftests/ftrace: Add new test case which checks for optimized probes Akanksha J N
2023-04-30 1:52 ` Masami Hiramatsu
2023-05-08 17:36 ` Shuah Khan [this message]
2023-05-12 22:15 ` Steven Rostedt
2023-05-17 16:26 ` Shuah Khan
2023-05-18 4:29 ` 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=54bec864-5e4f-8432-a331-e4ea5fc2ba31@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--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=naveen.n.rao@linux.ibm.com \
--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