One of the arguments I've heard against adding static trace points is that they become part of the kernel ABI and can no longer be removed if they prove not to be useful. Perhaps a way around this argument would be to initially add tracepoints with a mangled name that depends on the current kernel release? That way, until a given set of tracepoints have proved themselves, any scripts using them would have to be updated with every kernel release in order to keep working. The mangling needn't be very complex (e.g. all tracepoints in 2.6.32 which might be removed at a later time could have "dot32" pre-pended to their names), it just needs to be unpredictable in future kernel releases.