From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2 v3] ftracetest: Add a couple of ftrace test cases
Date: Wed, 05 Nov 2014 17:41:15 +0900 [thread overview]
Message-ID: <5459E2AB.8020009@hitachi.com> (raw)
In-Reply-To: <87zjc6ulry.fsf@sejong.aot.lge.com>
(2014/11/05 16:52), Namhyung Kim wrote:
> Hi Steve,
>
> On Tue, 04 Nov 2014 10:28:47 -0500, Steven Rostedt wrote:
>> +count=`cat trace | grep '()' | grep -v schedule | wc -l`
>> +
>> +if [ $count -ne 0 ]; then
>> + echo "Graph filtering not working after stack tracer disabled?"
>> + exit -1
>> +fi
>> +
>> +count=`cat trace | grep 'schedule()' | wc -l`
>> +if [ $count -eq 0 ]; then
>> + echo "No schedule traces found?"
>> + exit -1
>
> Hmm.. in this case don't we need to call do_reset especially for the
> last testcase? Maybe we could define a simple function like:
>
> fail() { # msg
> do_reset
> echo $1
> exit -1
> }
If you want to call do_reset always on exit, you can also use "trap do_reset 0" too.
Thank you,
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-11-05 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 15:28 [PATCH 0/2 v3] ftracetest: Add ftrace tests to ftracetests Steven Rostedt
2014-11-04 15:28 ` [PATCH 1/2 v3] ftracetest: Add functions file that holds helper functions Steven Rostedt
2014-11-04 15:28 ` [PATCH 2/2 v3] ftracetest: Add a couple of ftrace test cases Steven Rostedt
2014-11-05 7:52 ` Namhyung Kim
2014-11-05 8:41 ` Masami Hiramatsu [this message]
2014-11-05 22:53 ` Steven Rostedt
2014-11-05 23:05 ` [PATCH 2/2 v4] " Steven Rostedt
2014-11-06 1:58 ` Namhyung Kim
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=5459E2AB.8020009@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).