From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, naresh.kamboju@linaro.org
Subject: Re: [PATCH 2/2] selftests: ftrace: Add more verbosity for immediate log
Date: Tue, 4 Jul 2017 00:57:03 +0900 [thread overview]
Message-ID: <20170704005703.a6d06d949bef84bc81148ba7@kernel.org> (raw)
In-Reply-To: <20170703091936.339ce3db@gandalf.local.home>
On Mon, 3 Jul 2017 09:19:36 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 3 Jul 2017 14:26:40 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Add 3-level verbosity for showing traced command log
> > on console immediately. Since some test cases can cause
> > kernel pacic if there is a probrem (like regression etc.),
> > we can not know which command caused the problem without
> > traced command log. This verbosity (-vvv) solves that
> > because it shows the log on console immediately. User
> > can get continuous command/error log.
> >
> > Note that this is a kind of kernel debug mode, if you
> > don't see any kernel related issue, you don't need this
> > verbosity.
> >
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> > ---
> > tools/testing/selftests/ftrace/ftracetest | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> > index 290cd42..e3f1521 100755
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -15,6 +15,7 @@ echo " -h|--help Show help message"
> > echo " -k|--keep Keep passed test logs"
> > echo " -v|--verbose Increase verbosity of test messages"
> > echo " -vv Alias of -v -v (Show all results in stdout)"
> > +echo " -vvv Alias of -v -v -v (Show all commands immediately)"
> > echo " -d|--debug Debug mode (trace all shell commands)"
> > echo " -l|--logdir <dir> Save logs on the <dir>"
> > exit $1
> > @@ -56,9 +57,10 @@ parse_opts() { # opts
> > KEEP_LOG=1
> > shift 1
> > ;;
> > - --verbose|-v|-vv)
> > + --verbose|-v|-vv|-vvv)
> > VERBOSE=$((VERBOSE + 1))
> > [ $1 = '-vv' ] && VERBOSE=$((VERBOSE + 1))
> > + [ $1 = '-vvv' ] && VERBOSE=$((VERBOSE + 2))
> > shift 1
> > ;;
> > --debug|-d)
> > @@ -252,7 +254,9 @@ run_test() { # testfile
> > testcase $1
> > echo "execute$INSTANCE: "$1 > $testlog
> > SIG_RESULT=0
> > - if [ $VERBOSE -ge 2 ]; then
> > + if [ $VERBOSE -ge 3 ]; then
> > + __run_test $1 | tee -a $testlog 2>&1
>
> I have nothing against this patch, but I want to point out that the
> above is far from printing everything out immediately. The tee command
> buffers a bit. At least it has for me in the past. If the kernel does
> crash, one needs to still be a bit weary of where exactly the crash
> happened.
Indeed.
> Perhaps we need an option to print not to a log, but just let the test
> print out directly?
OK, then I'd like to add "--logdir -" option instead of this.
(if someone can correct console log, they may not need logfile)
Thank you,
>
> -- Steve
>
>
>
> > + elif [ $VERBOSE -eq 2 ]; then
> > __run_test $1 2>> $testlog | tee -a $testlog
> > else
> > __run_test $1 >> $testlog 2>&1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-07-03 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 5:25 [PATCH 1/2] selftests: ftrace: Do not failure if there is unsupported tests Masami Hiramatsu
2017-07-03 5:26 ` [PATCH 2/2] selftests: ftrace: Add more verbosity for immediate log Masami Hiramatsu
2017-07-03 13:19 ` Steven Rostedt
2017-07-03 15:57 ` Masami Hiramatsu [this message]
2017-07-03 13:15 ` [PATCH 1/2] selftests: ftrace: Do not failure if there is unsupported tests Steven Rostedt
2017-07-03 15:52 ` Masami Hiramatsu
2017-07-03 15:59 ` Steven Rostedt
2017-07-04 0:30 ` 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=20170704005703.a6d06d949bef84bc81148ba7@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=rostedt@goodmis.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
Powered by JetHome