From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: Ftrace startup test and boot-time tracing
Date: Mon, 7 Dec 2020 18:38:42 -0500 [thread overview]
Message-ID: <20201207183842.5374eed6@gandalf.local.home> (raw)
In-Reply-To: <20201208082649.93bdd57eb397296c81baf64c@kernel.org>
On Tue, 8 Dec 2020 08:26:49 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Hi Steve,
>
> On Mon, 7 Dec 2020 15:25:40 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Mon, 7 Dec 2020 23:02:59 +0900
> > Masami Hiramatsu <mhiramat@kernel.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
next prev parent reply other threads:[~2020-12-07 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 14:02 Ftrace startup test and boot-time tracing Masami Hiramatsu
2020-12-07 20:25 ` Steven Rostedt
2020-12-07 23:26 ` Masami Hiramatsu
2020-12-07 23:38 ` Steven Rostedt [this message]
2020-12-08 8:54 ` [PATCH] tracing: Disable ftrace selftests when any tracer is running 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=20201207183842.5374eed6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).