Re: [PATCH v3 14/14] tracing/selftest: Add test to test hist trigger between kernel event and trace_marker
From: Steven Rostedt
Date: Fri May 25 2018 - 14:15:15 EST
On Wed, 23 May 2018 23:15:59 +0900
Masami Hiramatsu <mhiramat@xxxxxxxxxx> wrote:
> On Wed, 16 May 2018 11:00:26 -0400
> Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
>
> > From: "Steven Rostedt (VMware)" <rostedt@xxxxxxxxxxx>
> >
> > Add a test that tests a trigger that is initiated by a kernel event
> > (sched_waking) and compared to a write to the trace_marker.
> >
> > Signed-off-by: Steven Rostedt (VMware) <rostedt@xxxxxxxxxxx>
> > ---
> > .../trigger/trigger-trace-marker-synthetic.tc | 22 +++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> > diff --git a/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-synthetic.tc b/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-synthetic.tc
> > index 3666dd6ab02a..b06996ecd5e0 100644
> > --- a/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-synthetic.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-synthetic.tc
> > @@ -31,6 +31,11 @@ if [ ! -d events/ftrace/print ]; then
> > exit_unsupported
> > fi
> >
> > +if [ ! -d events/sched/sched_waking ]; then
> > + echo "event sched_waking is not supported"
> > + exit_unsupported
> > +fi
>
> Hmm, this looks no good sign... Can you split this out to another testcase,
> since this check is only for new test case below?
>
You mean like this?
-- Steve