public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: linux-kselftest@vger.kernel.org, shuah@kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest
Date: Tue, 23 May 2017 15:02:38 +0900	[thread overview]
Message-ID: <149551934796.30231.12544755801380678045.stgit@devbox> (raw)

Hi,

This series improves ftracetest mainly to run on 4.9 stable
tree kernel. There still some issues remains (it seems some
fixes are not merged), but a half of issues are fixed.

NOTE: One patch will modify ftrace README to check the
availability of the maxactive option, which should have
been implemented with the function-added patch.

With this series, only 1 test actually failed on 4.9.29.
(and 3 unsupported, since it is too old to support it)

Tue May 23 05:56:24 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 [FAIL]
[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     [UNSUPPORTED]
[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      [UNSUPPORTED]
[40] (instance)  ftrace - test for function traceon/off triggers        [UNSUPPORTED]
[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:  41
# of failed:  1
# of unresolved:  0
# of untested:  0
# of unsupported:  3
# of xfailed:  0
# of undefined(test bug):  0


> [15] ftrace - test reading of set_ftrace_filter [FAIL]
was caused by the difference of the result of 
"dd bs=1 if=set_ftrace_filter" and "cat set_ftrace_filter",
which has been fixed on upstream by commit fcdc71257923
("ftrace: Fix indexing of t_hash_start() from t_next()")
but backporting it onto 4.9.y stable tree didn't fix that.


Thank you,

---

Masami Hiramatsu (7):
      selftests/ftrace: Skip full-glob-matching filter test on older kernel
      selftests/ftrace: Reduce trace buffer checking overhead
      ftrace/kprobes: selftests: Check kretprobe maxactive is supported
      selftests/ftrace: Reset ftrace filter on older kernel
      selftests/ftrace: Add instance indication in test log
      selftests/ftrace: Use top-level available_filter_function
      selftests/ftrace: Return unsupported if it detects older kernel


 kernel/trace/trace.c                               |    3 +-
 tools/testing/selftests/ftrace/ftracetest          |    2 +
 .../ftrace/test.d/event/toplevel-enable.tc         |    8 ++++--
 .../ftrace/test.d/ftrace/func-filter-glob.tc       |   28 ++++++++++++--------
 .../ftrace/test.d/ftrace/func_event_triggers.tc    |    9 ++++++
 .../test.d/ftrace/func_traceonoff_triggers.tc      |   13 +++++++++
 .../ftrace/test.d/instances/instance-event.tc      |    5 +++-
 .../ftrace/test.d/kprobe/kretprobe_maxactive.tc    |    1 +
 8 files changed, 53 insertions(+), 16 deletions(-)

--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>

             reply	other threads:[~2017-05-23  6:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  6:02 Masami Hiramatsu [this message]
2017-05-23  6:03 ` [PATCH 1/7] selftests/ftrace: Skip full-glob-matching filter test on older kernel Masami Hiramatsu
2017-05-23  6:04 ` [PATCH 2/7] selftests/ftrace: Reduce trace buffer checking overhead Masami Hiramatsu
2017-05-23  6:05 ` [PATCH 3/7] ftrace/kprobes: selftests: Check kretprobe maxactive is supported Masami Hiramatsu
2017-05-23  6:06 ` [PATCH 4/7] selftests/ftrace: Reset ftrace filter on older kernel Masami Hiramatsu
2017-05-23  6:07 ` [PATCH 5/7] selftests/ftrace: Add instance indication in test log Masami Hiramatsu
2017-05-23  6:09 ` [PATCH 6/7] selftests/ftrace: Use top-level available_filter_function Masami Hiramatsu
2017-05-23  6:10 ` [PATCH 7/7] selftests/ftrace: Return unsupported if it detects older kernel Masami Hiramatsu
2017-06-07 22:42 ` [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest Shuah Khan
2017-06-07 22:56   ` Steven Rostedt
2017-06-07 23:01     ` Shuah Khan
2017-06-08 17:37       ` Steven Rostedt
2017-06-08 20:06         ` Shuah Khan
2017-06-08 21:08           ` Steven Rostedt
2017-06-08 21:14             ` Shuah Khan
2017-06-08 21:26               ` Steven Rostedt
2017-06-08 21:33                 ` Shuah Khan
2017-06-08 21:39                   ` Steven Rostedt
2017-06-08 21:44                     ` Shuah Khan
2017-06-08 21:51                       ` Steven Rostedt
2017-06-14  2:12                         ` Masami Hiramatsu
2017-06-14  4:53                           ` Masami Hiramatsu
2017-06-14 14:17                             ` Shuah Khan
2017-06-30 14:18                               ` Shuah Khan
2017-06-08 21:11       ` 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=149551934796.30231.12544755801380678045.stgit@devbox \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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