mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linyu Yuan <quic_linyyuan@quicinc.com>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Tom Zanussi <zanussi@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] selftests/ftrace: add test case for GRP/ only input
Date: Thu, 2 Jun 2022 09:14:26 +0800	[thread overview]
Message-ID: <44ae3cc5-12ea-ada3-aee9-2b572c2343f7@quicinc.com> (raw)
In-Reply-To: <20220601235744.93ba3c80951680c3d6bb6961@kernel.org>

hi Masami,

thanks for review, will update your comment in next V4.

thanks

On 6/1/2022 10:57 PM, Masami Hiramatsu (Google) wrote:
> Hi Linyu,
>
> On Tue, 31 May 2022 14:29:12 +0800
> Linyu Yuan <quic_linyyuan@quicinc.com> wrote:
>
>> add kprobe and eprobe event test for new GRP/ only format.
>>
>> Signed-off-by: Linyu Yuan <quic_linyyuan@quicinc.com>
>> ---
>> v3: first add in this version
>>
>>   .../testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc  | 7 ++++++-
>>   .../testing/selftests/ftrace/test.d/dynevent/add_remove_kprobe.tc  | 7 ++++++-
>>   2 files changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
>> index 60c02b4..97856df 100644
>> --- a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
>> +++ b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
>> @@ -1,7 +1,7 @@
>>   #!/bin/sh
>>   # SPDX-License-Identifier: GPL-2.0
>>   # description: Generic dynamic event - add/remove eprobe events
>> -# requires: dynamic_events events/syscalls/sys_enter_openat "e[:[<group>/]<event>] <attached-group>.<attached-event> [<args>]":README
>> +# requires: dynamic_events events/syscalls/sys_enter_openat "e[:[<group>/][<event>]] <attached-group>.<attached-event> [<args>]":README
> Hmm, this is too restricted. With this change, this entire test only runs after
> patching this series.
> Can you change the requires so that skip checking the first half, like
>    "<attached-group>.<attached-event> [<args>]":README
> and check whether "e[:[<group>/][<event>]]" is in the README for the new
> test code?
>   
>>   echo 0 > events/enable
>>   
>> @@ -87,4 +87,9 @@ echo "-:eprobes/$EPROBE $SYSTEM/$EVENT $OPTIONS" >> dynamic_events
>>   ! grep -q "$EPROBE" dynamic_events
>>   ! test -d events/eprobes/$EPROBE
>>   
>> +echo "e:mygroup/ $SYSTEM/$EVENT $OPTIONS" >> dynamic_events
>> +test -d events/mygroup
>> +echo "-:mygroup/" >> dynamic_events
>> +! test -d events/mygroup
>> +
>>   clear_trace
>> diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_kprobe.tc b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_kprobe.tc
>> index b4da41d..6b102a7 100644
>> --- a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_kprobe.tc
>> +++ b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_kprobe.tc
>> @@ -1,7 +1,7 @@
>>   #!/bin/sh
>>   # SPDX-License-Identifier: GPL-2.0
>>   # description: Generic dynamic event - add/remove kprobe events
>> -# requires: dynamic_events "place: [<module>:]<symbol>":README "place (kretprobe): [<module>:]<symbol>":README
>> +# requires: dynamic_events "p[:[<group>/][<event>]] <place> [<args>]":README
> Ditto. In this case, don't touch the requires line (because it is not
> updated) and just add a README check for below new code.
>
> Thank you,
>
>
>>   
>>   echo 0 > events/enable
>>   echo > dynamic_events
>> @@ -23,4 +23,9 @@ grep -q myevent1 dynamic_events
>>   
>>   echo > dynamic_events
>>   
>> +echo "p:mygroup/ $PLACE" >> dynamic_events
>> +test -d events/mygroup
>> +echo "-:mygroup/" >> dynamic_events
>> +! test -d events/mygroup
>> +
>>   clear_trace
>> -- 
>> 2.7.4
>>
>

      reply	other threads:[~2022-06-02  1:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31  6:29 [PATCH v3 0/3] [PATCH v2 0/2] tracing/probes: allow no event name input when create group Linyu Yuan
2022-05-31  6:29 ` [PATCH v3 1/3] tracing: eprobe: remove duplicate is_good_name() operation Linyu Yuan
2022-05-31  6:29 ` [PATCH v3 2/3] tracing: auto generate event name when create a group of events Linyu Yuan
2022-05-31  6:29 ` [PATCH v3 3/3] selftests/ftrace: add test case for GRP/ only input Linyu Yuan
2022-06-01 14:57   ` Masami Hiramatsu
2022-06-02  1:14     ` Linyu Yuan [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=44ae3cc5-12ea-ada3-aee9-2b572c2343f7@quicinc.com \
    --to=quic_linyyuan@quicinc.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

all inboxes | Powered by JetHome®