On Tue, 2013-02-12 at 13:21 -0500, Steven Rostedt wrote: > Perhaps the way to do this is to have certain tracepoints only appear > with a kernel parameter. Something like "enable_debug_tracepoints", > where distros will not have it enabled by default (the word "debug" > should scare them). And thus, tools should never use them. But for those > that need to debug systems, the kernel parameter can be added, and these > tracepoints will "magically" appear. > > I mean, do we have to support an ABI that requires a kernel parameter > set in order to use it? Actually, debug didn't scare them enough for > debugfs, maybe the parameter should be called: > "enable_unstable_tracepoints" That would be even scarier. Or have it be > "enable_tracepoints_but_do_not_expect_them_to_exist", but that wastes up > too much of the kernel parameter text. > 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. -- 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
