From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, 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: Re: [for-next][PATCH 0/5] selftests: ftrace: Tracing updates to allow instance testing
Date: Wed, 26 Apr 2017 01:05:45 +0900 [thread overview]
Message-ID: <20170426010545.525d755ccbfddafce7244b53@kernel.org> (raw)
In-Reply-To: <20170425132440.454688279@goodmis.org>
On Tue, 25 Apr 2017 09:24:40 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> for-next
>
> Head SHA1: d6322f6cc483bd512efd3360fa76d0286a5b528b
>
>
> Steven Rostedt (VMware) (5):
> selftests: ftrace: Allow some tests to be run in a tracing instance
> selftests: ftrace: Make func_event_triggers and func_traceonoff_triggers tests do instances
> selftests: ftrace: Have event tests also run in an tracing instance
> selftests: ftrace: Have some basic tests run in a tracing instance too
> selftests: ftrace: Allow some event trigger tests to run in an instance
>
> ----
> tools/testing/selftests/ftrace/ftracetest | 18 +++++++++++++++++-
> .../testing/selftests/ftrace/test.d/00basic/basic2.tc | 1 +
> .../testing/selftests/ftrace/test.d/00basic/basic3.tc | 1 +
> .../selftests/ftrace/test.d/event/event-enable.tc | 1 +
> .../testing/selftests/ftrace/test.d/event/event-pid.tc | 1 +
> .../selftests/ftrace/test.d/event/subsystem-enable.tc | 1 +
> .../ftrace/test.d/ftrace/func_event_triggers.tc | 1 +
> .../ftrace/test.d/ftrace/func_traceonoff_triggers.tc | 1 +
> .../ftrace/test.d/trigger/trigger-eventonoff.tc | 1 +
> .../selftests/ftrace/test.d/trigger/trigger-filter.tc | 1 +
> .../ftrace/test.d/trigger/trigger-hist-mod.tc | 1 +
> .../selftests/ftrace/test.d/trigger/trigger-hist.tc | 1 +
> .../ftrace/test.d/trigger/trigger-multihist.tc | 1 +
> 13 files changed, 29 insertions(+), 1 deletion(-)
I've reviewed & tested the series. Looks good to me.
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
for the series.
Tue Apr 25 16:02:40 UTC 2017
=== Ftrace unit tests ===
[1] Basic trace file check [PASS]
[2] Basic test for tracers [PASS]
[3] Basic trace clock test [PASS]
[4] Basic event tracing check [PASS]
[5] event tracing - enable/disable with event level files [PASS]
[6] event tracing - restricts events based on pid [PASS]
[7] event tracing - enable/disable with subsystem level files [PASS]
[8] event tracing - enable/disable with top level files [PASS]
[9] ftrace - function graph filters with stack tracer [PASS]
[10] ftrace - function graph filters [PASS]
[11] ftrace - function glob filters [PASS]
[12] ftrace - function pid filters [PASS]
[13] ftrace - test for function event triggers [PASS]
[14] ftrace - function profiler with function tracing [PASS]
[15] ftrace - test reading of set_ftrace_filter [PASS]
[16] ftrace - test for function traceon/off triggers [PASS]
[17] Test creation and deletion of trace instances while setting an event [PASS]
[18] Test creation and deletion of trace instances [PASS]
[19] Kprobe dynamic event - adding and removing [PASS]
[20] Kprobe dynamic event - busy event check [PASS]
[21] Kprobe dynamic event with arguments [PASS]
[22] Kprobes event arguments with types [PASS]
[23] Kprobe dynamic event with function tracer [PASS]
[24] Kretprobe dynamic event with arguments [PASS]
[25] Kretprobe dynamic event with maxactive [PASS]
[26] event trigger - test event enable/disable trigger [PASS]
[27] event trigger - test trigger filter [PASS]
[28] event trigger - test histogram modifiers [PASS]
[29] event trigger - test histogram trigger [PASS]
[30] event trigger - test multiple histogram triggers [PASS]
[31] event trigger - test snapshot-trigger [PASS]
[32] event trigger - test stacktrace-trigger [PASS]
[33] event trigger - test traceon/off trigger [PASS]
[34] (instance) Basic test for tracers [PASS]
[35] (instance) Basic trace clock test [PASS]
[36] (instance) event tracing - enable/disable with event level files [PASS]
[37] (instance) event tracing - restricts events based on pid [PASS]
[38] (instance) event tracing - enable/disable with subsystem level files [PASS]
[39] (instance) ftrace - test for function event triggers [PASS]
[40] (instance) ftrace - test for function traceon/off triggers [PASS]
[41] (instance) event trigger - test event enable/disable trigger [PASS]
[42] (instance) event trigger - test trigger filter [PASS]
[43] (instance) event trigger - test histogram modifiers [PASS]
[44] (instance) event trigger - test histogram trigger [PASS]
[45] (instance) event trigger - test multiple histogram triggers [PASS]
# of passed: 45
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-04-25 16:06 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 ` [for-next][PATCH 4/5] selftests: ftrace: Have some basic tests run in a tracing instance too Steven Rostedt
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 ` Masami Hiramatsu [this message]
2017-04-26 2:07 ` [for-next][PATCH 0/5] selftests: ftrace: Tracing updates to allow instance testing 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=20170426010545.525d755ccbfddafce7244b53@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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