On Mon, 2 Nov 2015 17:42:43 -0500 Mathieu Desnoyers <[email protected]> wrote:
> In order to use ftrace tracers to generate tracepoints without doing > tracing to its own hardcoded ring buffers, add a ftrace-buffer option > (default: 1). When set to 0, it disables tracing into the ftrace > hardcoded buffers. > This should be a tracer specific option. And it shouldn't be called "ftrace-buffer" as that is a very confusing name. Perhaps I can add an option that will prevent the snapshots as well. Perhaps an option called "quiet", and a "no_snapshot" one too. I can create the no snapshot one. But this should be converted to "quiet" and added as a tracer specific option. -- Steve > Signed-off-by: Mathieu Desnoyers <[email protected]> > CC: Thomas Gleixner <[email protected]> > CC: Steven Rostedt <[email protected]> > CC: Ingo Molnar <[email protected]> > CC: Peter Zijlstra <[email protected]> > --- > kernel/trace/trace.c | 4 +++- > kernel/trace/trace.h | 1 + > kernel/trace/trace_irqsoff.c | 19 +++++++++++-------- > 3 files changed, 15 insertions(+), 9 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
