From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [RFC PATCH 0/4 v2] ftracetests: Add ftrace tests to ftracetests
Date: Mon, 03 Nov 2014 16:27:37 -0500 [thread overview]
Message-ID: <20141103212737.696365174@goodmis.org> (raw)
Second attempt. I took the advice from Masami Hiramatsu and modified
my tests. I also added some helper functions to ftracetests as well.
I split the one function graph test into two. One to just test the
filtering of the function graph and another to test with stack tracer.
Steven Rostedt (Red Hat) (4):
ftracetest: Add clear_trace() helper to reset the trace file
ftracetest: Add disable/enable_tracing() helper calls
ftracetest: Add helper reset_tracer() function
ftracetest: Add a couple of ftrace test cases
----
tools/testing/selftests/ftrace/ftracetest | 3 +
.../ftrace/test.d/ftrace/fgraph-filter-stack.tc | 94 ++++++++++++++++++++++
.../ftrace/test.d/ftrace/fgraph-filter.tc | 49 +++++++++++
.../ftrace/test.d/ftrace/func_profiler.tc | 76 +++++++++++++++++
tools/testing/selftests/ftrace/test.d/functions | 16 ++++
5 files changed, 238 insertions(+)
next reply other threads:[~2014-11-03 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 21:27 Steven Rostedt [this message]
2014-11-03 21:27 ` [RFC PATCH 1/4 v2] ftracetest: Add clear_trace() helper to reset the trace file Steven Rostedt
2014-11-03 21:27 ` [RFC PATCH 2/4 v2] ftracetest: Add disable/enable_tracing() helper calls Steven Rostedt
2014-11-03 21:27 ` [RFC PATCH 3/4 v2] ftracetest: Add helper reset_tracer() function Steven Rostedt
2014-11-03 21:27 ` [RFC PATCH 4/4 v2] ftracetest: Add a couple of ftrace test cases Steven Rostedt
2014-11-04 8:31 ` Namhyung Kim
2014-11-04 14:03 ` Steven Rostedt
2014-11-04 5:59 ` [RFC PATCH 0/4 v2] ftracetests: Add ftrace tests to ftracetests Masami Hiramatsu
2014-11-04 9:30 ` Masami Hiramatsu
2014-11-04 14:03 ` 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=20141103212737.696365174@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@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