mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/5] [GIT PULL] ftracetest/tools/selftests: Self tests to test ftrace
Date: Wed, 08 Oct 2014 14:03:41 -0400	[thread overview]
Message-ID: <20141008180341.252728944@goodmis.org> (raw)


Linus,

This patch series starts a new selftests section in the
tools/testing/selftest directory called "ftrace" that holds tests
aimed at testing ftrace and subsystems that use ftrace (like kprobes).

So far only a few tests were written (by Masami Hiramatsu), but more will
be added in the near future (3.19).

Please pull the latest ftracetest-3.18 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
ftracetest-3.18

Tag SHA1: 82533f8d106661960f4675f5f3248c00e9157f49
Head SHA1: 89c5497d1f933af56dac617f0fd86150942a7fb6


Masami Hiramatsu (5):
      ftracetest: Initial commit for ftracetest
      ftracetest: Add ftrace basic testcases
      ftracetest: Add kprobe basic testcases
      ftracetest: Add POSIX.3 standard and XFAIL result codes
      tracing/kprobes: Add selftest scripts testing kprobe-tracer as startup test

----
 MAINTAINERS                                        |   1 +
 tools/testing/selftests/Makefile                   |   1 +
 tools/testing/selftests/ftrace/Makefile            |   7 +
 tools/testing/selftests/ftrace/README              |  82 +++++++
 tools/testing/selftests/ftrace/ftracetest          | 253 +++++++++++++++++++++
 tools/testing/selftests/ftrace/samples/fail.tc     |   4 +
 tools/testing/selftests/ftrace/samples/pass.tc     |   3 +
 .../testing/selftests/ftrace/samples/unresolved.tc |   4 +
 .../selftests/ftrace/samples/unsupported.tc        |   3 +
 tools/testing/selftests/ftrace/samples/untested.tc |   3 +
 tools/testing/selftests/ftrace/samples/xfail.tc    |   3 +
 .../selftests/ftrace/test.d/00basic/basic1.tc      |   3 +
 .../selftests/ftrace/test.d/00basic/basic2.tc      |   7 +
 .../selftests/ftrace/test.d/00basic/basic3.tc      |   8 +
 .../ftrace/test.d/kprobe/add_and_remove.tc         |  11 +
 .../selftests/ftrace/test.d/kprobe/busy_check.tc   |  13 ++
 .../selftests/ftrace/test.d/kprobe/kprobe_args.tc  |  16 ++
 .../ftrace/test.d/kprobe/kretprobe_args.tc         |  15 ++
 tools/testing/selftests/ftrace/test.d/template     |   9 +
 19 files changed, 446 insertions(+)

             reply	other threads:[~2014-10-08 18:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 18:03 Steven Rostedt [this message]
2014-10-08 18:03 ` [PATCH 1/5] ftracetest: Initial commit for ftracetest Steven Rostedt
2014-10-08 18:03 ` [PATCH 2/5] ftracetest: Add ftrace basic testcases Steven Rostedt
2014-10-08 18:03 ` [PATCH 3/5] ftracetest: Add kprobe " Steven Rostedt
2014-10-08 18:03 ` [PATCH 4/5] ftracetest: Add POSIX.3 standard and XFAIL result codes Steven Rostedt
2014-10-08 18:03 ` [PATCH 5/5] tracing/kprobes: Add selftest scripts testing kprobe-tracer as startup test 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=20141008180341.252728944@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=torvalds@linux-foundation.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

Powered by JetHome