[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200319220435.0f1830f9d11cc05befee26e8@kernel.org>
Date: Thu, 19 Mar 2020 22:04:35 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Shuah Khan <shuahkhan@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Peter Wu <peter@...ensteyn.nl>,
Jonathan Corbet <corbet@....net>,
Tom Zanussi <zanussi@...nel.org>,
linux-kselftest@...r.kernel.org, skhan@...uxfoundation.org
Subject: Re: [RFC][PATCH 12/11] selftest/ftrace: Fix function trigger test
to handle trace not disabling the tracer
On Wed, 18 Mar 2020 10:35:29 -0600
Shuah Khan <shuahkhan@...il.com> wrote:
> On Wed, Mar 18, 2020 at 9:13 AM Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> >
> > From: "Steven Rostedt (VMware)" <rostedt@...dmis.org>
> >
> > The ftrace selftest "ftrace - test for function traceon/off triggers"
> > enables all events and reads the trace file. Now that the trace file does
> > not disable tracing, and will attempt to continually read new data that is
> > added, the selftest gets stuck reading the trace file. This is because the
> > data added to the trace file will fill up quicker than the reading of it.
> >
> > By only enabling scheduling events, the read can keep up with the writes.
> > Instead of enabling all events, only enable the scheduler events.
> >
> > Signed-off-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
Looks good to me.
Acked-by: Masami Hiramatsu <mhiramat@...nel.org>
Thanks!
> > ---
> > .../selftests/ftrace/test.d/ftrace/func_traceonoff_triggers.tc | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> + linux-kselttest and my LF email.
>
> thanks,
> -- Shuah
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists