From: Po-Hsu Lin <po-hsu.lin@canonical.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kselftest@vger.kernel.org, mingo@redhat.com,
shuah <shuah@kernel.org>, Colin King <colin.king@canonical.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Xiao Yang <yangx.jy@cn.fujitsu.com>,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/ftrace: treat module requirement unmet situation as unsupported
Date: Thu, 30 Apr 2020 09:46:36 +0800 [thread overview]
Message-ID: <CAMy_GT88BD6Ty9=gtqhsm2UPf8aX-=SHZrWj_-UZJONnk73+nQ@mail.gmail.com> (raw)
In-Reply-To: <20200429122855.02594f33@gandalf.local.home>
On Thu, Apr 30, 2020 at 12:29 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 29 Apr 2020 17:50:44 +0800
> Po-Hsu Lin <po-hsu.lin@canonical.com> wrote:
>
> > When the required module for the test does not exist, use
> > exit_unsupported instead of exit_unresolved to indicate this test is
> > not supported.
> >
> > By doing this we can make test behaviour in sync with the
> > irqsoff_tracer.tc test in preemptirq, which is also treating module
> > existence in this way. Moreover, the test won't exit with a non-zero
> > return value if the module does not exist.
> >
> > Fixes: 646f01ccdd59 ("ftrace/selftest: Add tests to test register_ftrace_direct()")
> > Fixes: 4d23e9b4fd2e ("selftests/ftrace: Add trace_printk sample module test")
> > Fixes: 7bc026d6c032 ("selftests/ftrace: Add function filter on module testcase")
> > Fixes: af2a0750f374 ("selftests/ftrace: Improve kprobe on module testcase to load/unload module")
>
> I don't think this deserves the Fixes tags.
Hello Steven,
OK I will remove these Fixes tags and resubmit V2 if Masami agrees
with this change.
>
> > Signed-off-by: Po-Hsu Lin <po-hsu.lin@canonical.com>
> > ---
> > tools/testing/selftests/ftrace/test.d/direct/ftrace-direct.tc | 2 +-
> > tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc | 2 +-
> > tools/testing/selftests/ftrace/test.d/event/trace_printk.tc | 2 +-
> > tools/testing/selftests/ftrace/test.d/ftrace/func_mod_trace.tc | 2 +-
> > tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc | 2 +-
>
> I'm fine with these changes if Masami is. But it is Masami's call as his
> infrastructure is more sensitive to the return calls than mine. I just run
> the test and see what passes. I don't actually look at the return codes.
Another thing to note is that this will also change the "# of
unresolved" and "# of unsupported" in the summary at the end of the
test report.
Thanks
Po-Hsu
>
> -- Steve
>
>
> > 5 files changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/test.d/direct/ftrace-direct.tc b/tools/testing/selftests/ftrace/test.d/direct/ftrace-direct.tc
> > index d75a869..3d6189e 100644
> > --- a/tools/testing/selftests/ftrace/test.d/direct/ftrace-direct.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/direct/ftrace-direct.tc
> > @@ -5,7 +5,7 @@
> > rmmod ftrace-direct ||:
> > if ! modprobe ftrace-direct ; then
> > echo "No ftrace-direct sample module - please make CONFIG_SAMPLE_FTRACE_DIRECT=m"
> > - exit_unresolved;
> > + exit_unsupported;
> > fi
> >
> > echo "Let the module run a little"
> > diff --git a/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc b/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc
> > index 801ecb6..3d0e3ca 100644
> > --- a/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc
> > @@ -5,7 +5,7 @@
> > rmmod ftrace-direct ||:
> > if ! modprobe ftrace-direct ; then
> > echo "No ftrace-direct sample module - please build with CONFIG_SAMPLE_FTRACE_DIRECT=m"
> > - exit_unresolved;
> > + exit_unsupported;
> > fi
> >
> > if [ ! -f kprobe_events ]; then
> > diff --git a/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc b/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
> > index b02550b..dd8b10d 100644
> > --- a/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
> > @@ -5,7 +5,7 @@
> > rmmod trace-printk ||:
> > if ! modprobe trace-printk ; then
> > echo "No trace-printk sample module - please make CONFIG_SAMPLE_TRACE_PRINTK=m"
> > - exit_unresolved;
> > + exit_unsupported;
> > fi
> >
> > echo "Waiting for irq work"
> > diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/func_mod_trace.tc b/tools/testing/selftests/ftrace/test.d/ftrace/func_mod_trace.tc
> > index 1a4b4a4..26dc06a 100644
> > --- a/tools/testing/selftests/ftrace/test.d/ftrace/func_mod_trace.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/ftrace/func_mod_trace.tc
> > @@ -13,7 +13,7 @@ echo '*:mod:trace_printk' > set_ftrace_filter
> > if ! modprobe trace-printk ; then
> > echo "No trace-printk sample module - please make CONFIG_SAMPLE_TRACE_PRINTK=
> > m"
> > - exit_unresolved;
> > + exit_unsupported;
> > fi
> >
> > : "Wildcard should be resolved after loading module"
> > diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc
> > index d861bd7..4e07c69 100644
> > --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc
> > @@ -8,7 +8,7 @@ rmmod trace-printk ||:
> > if ! modprobe trace-printk ; then
> > echo "No trace-printk sample module - please make CONFIG_SAMPLE_TRACE_PRINTK=
> > m"
> > - exit_unresolved;
> > + exit_unsupported;
> > fi
> >
> > MOD=trace_printk
>
next prev parent reply other threads:[~2020-04-30 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:50 [PATCH] selftests/ftrace: treat module requirement unmet situation as unsupported Po-Hsu Lin
2020-04-29 11:29 ` Xiao Yang
2020-04-29 16:28 ` Steven Rostedt
2020-04-30 1:46 ` Po-Hsu Lin [this message]
2020-04-30 2:04 ` Steven Rostedt
2020-05-01 1:59 ` Masami Hiramatsu
2020-05-04 8:45 ` Po-Hsu Lin
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='CAMy_GT88BD6Ty9=gtqhsm2UPf8aX-=SHZrWj_-UZJONnk73+nQ@mail.gmail.com' \
--to=po-hsu.lin@canonical.com \
--cc=colin.king@canonical.com \
--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=skhan@linuxfoundation.org \
--cc=yangx.jy@cn.fujitsu.com \
/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).