[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20211021093131.affc348280aba040f76f769e@kernel.org>
Date: Thu, 21 Oct 2021 09:31:31 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Li Zhijian <lizhijian@...fujitsu.com>, <mingo@...hat.com>,
<shuah@...nel.org>, <linux-kselftest@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Philip Li <philip.li@...el.com>,
kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] kselftests: ftrace: limit the executing time by reading
from cached trace
On Wed, 20 Oct 2021 10:16:59 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 20 Oct 2021 11:55:22 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
>
> > --- a/tools/testing/selftests/ftrace/test.d/functions
> > +++ b/tools/testing/selftests/ftrace/test.d/functions
> > @@ -124,6 +124,12 @@ initialize_ftrace() { # Reset ftrace to initial-state
> > [ -f uprobe_events ] && echo > uprobe_events
> > [ -f synthetic_events ] && echo > synthetic_events
> > [ -f snapshot ] && echo 0 > snapshot
> > +
> > +# Stop tracing while reading the trace file by default, to prevent
> > +# the test results while checking it and to avoid taking a long time
> > +# to check the result.
> > + [ -f options/pause-on-trace ] && echo 1 > options/pause-on-trace
> > +
>
> Is there a way we can save the previous setting and put it back on reset?
No, since each testcase must be run under the clean state. Would we need to
recover the settings?
Thank you,
>
> -- Steve
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists