On Tue, 2013-02-12 at 20:44 +0000, Al Viro wrote: > 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 ;-) Now this an interesting question. How much userspace must we guarantee, when the userspace that is used depends on a kernel change by a distro, and not mainline. Heck, we could make these tracepoints depend on lockdep. No production kernel will enable that. But I guess the distro could modify it to not depend on it, and then base on the tracepoint as is, and also complain. And the more hacks we do, the more difficult it is for us to use the tracepoints. :-p Bah! -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
