public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: [for-next][PATCH 4/5] selftests: ftrace: Have some basic tests run in a tracing instance too
Date: Tue, 25 Apr 2017 09:24:44 -0400	[thread overview]
Message-ID: <20170425132524.385102706@goodmis.org> (raw)
In-Reply-To: 20170425132440.454688279@goodmis.org

[-- Attachment #1: 0004-selftests-ftrace-Have-some-basic-tests-run-in-a-trac.patch --]
[-- Type: text/plain, Size: 1452 bytes --]

From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>

Some of the basic ftrace selftests should also be run in an instance. These
test a quick case of running all tracers in the available_tracers file
within the instance. The other is testing the clock used for the instance.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
 tools/testing/selftests/ftrace/test.d/00basic/basic2.tc | 1 +
 tools/testing/selftests/ftrace/test.d/00basic/basic3.tc | 1 +
 2 files changed, 2 insertions(+)

diff --git a/tools/testing/selftests/ftrace/test.d/00basic/basic2.tc b/tools/testing/selftests/ftrace/test.d/00basic/basic2.tc
index bf9a7b037924..ebfce83f35b4 100644
--- a/tools/testing/selftests/ftrace/test.d/00basic/basic2.tc
+++ b/tools/testing/selftests/ftrace/test.d/00basic/basic2.tc
@@ -1,5 +1,6 @@
 #!/bin/sh
 # description: Basic test for tracers
+# flags: instance
 test -f available_tracers
 for t in `cat available_tracers`; do
   echo $t > current_tracer
diff --git a/tools/testing/selftests/ftrace/test.d/00basic/basic3.tc b/tools/testing/selftests/ftrace/test.d/00basic/basic3.tc
index bde6625d9785..9e33f841812f 100644
--- a/tools/testing/selftests/ftrace/test.d/00basic/basic3.tc
+++ b/tools/testing/selftests/ftrace/test.d/00basic/basic3.tc
@@ -1,5 +1,6 @@
 #!/bin/sh
 # description: Basic trace clock test
+# flags: instance
 test -f trace_clock
 for c in `cat trace_clock | tr  -d \[\]`; do
   echo $c > trace_clock
-- 
2.10.2

  parent reply	other threads:[~2017-04-25 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 13:24 [for-next][PATCH 0/5] selftests: ftrace: Tracing updates to allow instance testing Steven Rostedt
2017-04-25 13:24 ` [for-next][PATCH 1/5] selftests: ftrace: Allow some tests to be run in a tracing instance Steven Rostedt
2017-04-25 13:24 ` [for-next][PATCH 2/5] selftests: ftrace: Make func_event_triggers and func_traceonoff_triggers tests do instances Steven Rostedt
2017-04-25 13:24 ` [for-next][PATCH 3/5] selftests: ftrace: Have event tests also run in an tracing instance Steven Rostedt
2017-04-25 13:24 ` Steven Rostedt [this message]
2017-04-25 13:24 ` [for-next][PATCH 5/5] selftests: ftrace: Allow some event trigger tests to run in an instance Steven Rostedt
2017-04-25 16:05 ` [for-next][PATCH 0/5] selftests: ftrace: Tracing updates to allow instance testing Masami Hiramatsu
2017-04-26  2:07 ` Namhyung Kim
2017-04-26 12:52   ` Steven Rostedt

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=20170425132524.385102706@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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