public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <shuah@kernel.org>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: [PATCH v3 2/7] selftests/ftrace: Return unsupported for the unconfigured features
Date: Wed,  3 Jun 2020 11:40:19 +0900	[thread overview]
Message-ID: <159115201908.70027.9721176218630572669.stgit@devnote2> (raw)
In-Reply-To: <159115200085.70027.6141550347953439240.stgit@devnote2>

As same as other test cases, return unsupported if kprobe_events
or argument access feature are not found.

There can be a new arch which does not port those features yet,
and an older kernel which doesn't support it.
Those can not enable the features.

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
---
 .../ftrace/test.d/direct/kprobe-direct.tc          |    2 +-
 .../ftrace/test.d/kprobe/kprobe_args_user.tc       |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

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 801ecb63e84c..e95b744b23e4 100644
--- a/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc
+++ b/tools/testing/selftests/ftrace/test.d/direct/kprobe-direct.tc
@@ -10,7 +10,7 @@ fi
 
 if [ ! -f kprobe_events ]; then
 	echo "No kprobe_events file -please build CONFIG_KPROBE_EVENTS"
-	exit_unresolved;
+	exit_unsupported;
 fi
 
 echo "Let the module run a little"
diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_user.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_user.tc
index 0f60087583d8..b41471f301ab 100644
--- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_user.tc
+++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_user.tc
@@ -4,7 +4,7 @@
 
 [ -f kprobe_events ] || exit_unsupported # this is configurable
 
-grep -q '\$arg<N>' README || exit_unresolved # depends on arch
+grep -q '\$arg<N>' README || exit_unsupported # depends on arch
 grep -A10 "fetcharg:" README | grep -q 'ustring' || exit_unsupported
 grep -A10 "fetcharg:" README | grep -q '\[u\]<offset>' || exit_unsupported
 


  parent reply	other threads:[~2020-06-03  2:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  2:40 [PATCH v3 0/7] selftsts/ftrace: Add requires list for each test case Masami Hiramatsu
2020-06-03  2:40 ` [PATCH v3 1/7] selftests/ftrace: Allow ":" in description Masami Hiramatsu
2020-06-03  2:40 ` Masami Hiramatsu [this message]
2020-06-03  2:40 ` [PATCH v3 3/7] selftests/ftrace: Add "requires:" list support Masami Hiramatsu
2020-06-03  2:40 ` [PATCH v3 4/7] selftests/ftrace: Convert required interface checks into requires list Masami Hiramatsu
2020-06-09 20:41   ` Shuah Khan
2020-06-10  5:55     ` Masami Hiramatsu
2020-06-10 12:04       ` Shuah Khan
2020-06-10 13:32         ` Steven Rostedt
2020-06-11 12:03           ` Shuah Khan
2020-06-11 14:36             ` Masami Hiramatsu
2020-06-16 16:48             ` Shuah Khan
2020-06-17 14:58               ` Masami Hiramatsu
2020-06-19 15:26                 ` Shuah Khan
2020-06-03  2:40 ` [PATCH v3 5/7] selftests/ftrace: Convert check_filter_file() with " Masami Hiramatsu
2020-06-03  2:40 ` [PATCH v3 6/7] selftests/ftrace: Support ":tracer" suffix for requires Masami Hiramatsu
2020-06-03  2:41 ` [PATCH v3 7/7] selftests/ftrace: Support ":README" " 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=159115201908.70027.9721176218630572669.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tom.zanussi@linux.intel.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