[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201207183842.5374eed6@gandalf.local.home>
Date: Mon, 7 Dec 2020 18:38:42 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>
Subject: Re: Ftrace startup test and boot-time tracing
On Tue, 8 Dec 2020 08:26:49 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> Hi Steve,
>
> On Mon, 7 Dec 2020 15:25:40 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Mon, 7 Dec 2020 23:02:59 +0900
> > Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > > There will be the 2 options, one is to change kconfig so that user can not
> > > select FTRACE_STARTUP_TEST if BOOTTIME_TRACING=y, another is to provide
> > > a flag from trace_boot and all tests checks the flag at runtime.
> > > (moreover, that flag will be good to be set from other command-line options)
> > > What would you think?
> >
> > Yeah, a "disable_ftrace_startup_tests" flag should be implemented. And
> > something that could also be on the kernel command line itself :-)
> >
> > "disabe_ftrace_startup_tests"
> >
> > Sometimes when debugging something, I don't want the tests running, even
> > though the config has them, and I don't want to change the config.
>
> OK, BTW, I found tracing_selftest_disabled, it seemed what we need.
>
Yeah, I thought we had something like this. It's getting hard to keep track
of ;-)
-- Steve
Powered by blists - more mailing lists