From: Al Viro <viro@ZenIV.linux.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-fsdevel@vger.kernel.org, chavey@google.com,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] vfs: make fcheck_files() an exported functions
Date: Tue, 12 Feb 2013 20:44:34 +0000 [thread overview]
Message-ID: <20130212204434.GP4503@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1360700468.21867.77.camel@gandalf.local.home>
On Tue, Feb 12, 2013 at 03:21:08PM -0500, Steven Rostedt wrote:
> Thinking about this a little more, we can call it
> "enable_unstable_tracepoints" and on boot up have a big banner that
> says:
>
>
> **************************************************************
> **************************************************************
> **** Unstable tracepoints enabled. Do not rely on them ****
> **************************************************************
> **************************************************************
>
> Have the boot up pause for 4 seconds displaying that. That text won't
> prevent distros from adding it as default, but the 4 second pause sure
> will :-)
>
> With all the work on fast boot up times, if we purposely slow down the
> kernel when enabled, no distro will want these enabled by default.
No, they'll just make that delay another kernel option ;-)
next prev parent reply other threads:[~2013-02-12 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:01 [PATCH 1/2] vfs: make fcheck_files() an exported functions Tejun Heo
2013-01-09 17:01 ` [PATCH 2/2] vfs: add fcheck tracepoint Tejun Heo
2013-02-09 19:24 ` [PATCH 1/2] vfs: make fcheck_files() an exported functions Tejun Heo
2013-02-10 0:18 ` Al Viro
2013-02-12 17:41 ` Tejun Heo
2013-02-12 18:21 ` Steven Rostedt
2013-02-12 20:21 ` Steven Rostedt
2013-02-12 20:44 ` Al Viro [this message]
2013-02-12 20:57 ` Steven Rostedt
2013-02-12 20:43 ` Al Viro
2013-02-12 21:03 ` Steven Rostedt
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=20130212204434.GP4503@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=chavey@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.