From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>,
Oleg Nesterov <oleg@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/3] ftrace: Add a ftrace test collection
Date: Tue, 05 Aug 2014 02:45:44 +0000 [thread overview]
Message-ID: <20140805024544.23693.66601.stgit@kbuild-fedora.novalocal> (raw)
Hi,
I'd like to introduce a collection of testcases for ftrace to
avoid regressions.
For a long time, we've tried to stabilize and extend ftrace
tracing infrastructure. This small test framework is a kind of
stabilizing work for ftrace. For the first step, this series
just introduces a few basic testcases. However, it is easy to
add additional tests. I'd like to ask you, ftrace developers,
to add tests for your features to ensure it will not be broken
by future works.
ftracetest is a tiny bash script so that anyone can easily
understand what it does. I think it is better to share and
discuss this tests before growing it.
- Is it enough to support bash script? (of course you can
invoke other commands from the script)
- What's the good naming method of testcases?
- Is any dependency check required?
BTW, I decided to put this under tools/testing/ftrace instead
of tools/testing/selftests/, because all tests requires root
privilege. It will be one of discussion points. Anyway,
it is easy to integrate this to the selftests.
Thank you,
---
Masami Hiramatsu (3):
ftracetest: Initial commit for ftracetest
ftracetest: Add ftrace basic testcases
ftracetest: Add kprobe basic testcases
tools/testing/ftrace/README | 38 ++++++
tools/testing/ftrace/ftracetest | 133 ++++++++++++++++++++
tools/testing/ftrace/test.d/basic1.tc | 3
tools/testing/ftrace/test.d/basic2.tc | 6 +
tools/testing/ftrace/test.d/basic3.tc | 8 +
.../testing/ftrace/test.d/kprobe/add_and_remove.tc | 11 ++
tools/testing/ftrace/test.d/kprobe/busy_check.tc | 14 ++
tools/testing/ftrace/test.d/template | 4 +
8 files changed, 217 insertions(+)
create mode 100644 tools/testing/ftrace/README
create mode 100755 tools/testing/ftrace/ftracetest
create mode 100644 tools/testing/ftrace/test.d/basic1.tc
create mode 100644 tools/testing/ftrace/test.d/basic2.tc
create mode 100644 tools/testing/ftrace/test.d/basic3.tc
create mode 100644 tools/testing/ftrace/test.d/kprobe/add_and_remove.tc
create mode 100644 tools/testing/ftrace/test.d/kprobe/busy_check.tc
create mode 100644 tools/testing/ftrace/test.d/template
--
next reply other threads:[~2014-08-05 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 2:45 Masami Hiramatsu [this message]
2014-08-05 2:45 ` [RFC PATCH 1/3] ftracetest: Initial commit for ftracetest Masami Hiramatsu
2014-08-05 2:45 ` [RFC PATCH 2/3] ftracetest: Add ftrace basic testcases Masami Hiramatsu
2014-08-05 2:46 ` [RFC PATCH 3/3] ftracetest: Add kprobe " Masami Hiramatsu
2014-08-05 21:37 ` [RFC PATCH 0/3] ftrace: Add a ftrace test collection Steven Rostedt
2014-08-07 4:53 ` Masami Hiramatsu
2014-08-13 6:59 ` Namhyung Kim
2014-08-13 7:14 ` Namhyung Kim
2014-08-13 15:54 ` 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=20140805024544.23693.66601.stgit@kbuild-fedora.novalocal \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.com \
--cc=yoshihiro.yunomae.ez@hitachi.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
all inboxes | Powered by JetHome®