From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>, shuah <shuah@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] ftrace/selftest: Fix ftracetest for non existant config and files
Date: Wed, 03 Jul 2019 15:49:59 -0400 [thread overview]
Message-ID: <20190703194959.596805445@goodmis.org> (raw)
Hi Masami,
I worked a bit more on the one issue that Po-Hsu found, and made it use
tracefs a bit more aggressively. To test this I ran the test on a 3.5
kernel and found another issue, where it failed because set_event_pid
and set_ftrace_pid did not exist.
Can you review these patches. I can take them in my tree, or if Shuah
would like, she can take it in hers (after you give a review).
Thanks!
-- Steve
Steven Rostedt (VMware) (2):
ftrace/selftests: Return the skip code when tracing directory not configured in kernel
ftrace/selftest: Test if set_event/ftrace_pid exists before writing
----
tools/testing/selftests/ftrace/ftracetest | 38 +++++++++++++++++++++----
tools/testing/selftests/ftrace/test.d/functions | 4 +--
2 files changed, 34 insertions(+), 8 deletions(-)
next reply other threads:[~2019-07-03 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 19:49 Steven Rostedt [this message]
2019-07-03 19:50 ` [PATCH 1/2] ftrace/selftests: Return the skip code when tracing directory not configured in kernel Steven Rostedt
2019-07-04 1:40 ` Masami Hiramatsu
2019-07-03 19:50 ` [PATCH 2/2] ftrace/selftest: Test if set_event/ftrace_pid exists before writing Steven Rostedt
2019-07-03 20:00 ` Steven Rostedt
2019-07-03 20:01 ` Steven Rostedt
2019-07-04 1:51 ` Masami Hiramatsu
2019-07-04 2:01 ` Steven Rostedt
2019-07-04 5:56 ` Masami Hiramatsu
2019-07-04 1:43 ` 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=20190703194959.596805445@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.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