[PATCH 0/3] tracing/ftrace: ftrace_bprintk

From: Frederic Weisbecker
Date: Tue Feb 24 2009 - 00:16:35 EST


Hi,

These three patches are part of a patchset posted by Lai Jiangshan in december 2008.
They introduce a binary version of ftrace_printk() called ftrace_bprintk()

While having the same goal: print a generic message entry into the ring buffer,
their approaches are very different.

- ftrace_printk() does the formatting job on tracing time, insert the whole resulting string
into the ring buffer, and then the string is printed on output time without a lot of modifications.

- ftrace_bprintk() does no formatting on tracing time. Instead, it looks at the format string
to find the types and the numbers of the arguments and directly stores them as-is into the
ring-buffer. Then the format string is stored into the ring-buffer too, but only by its address,
it is not copied. Then on output time only, the final string is formatted and sent to the user.
This gives a result about as fast as a traditional tracer with fixed fields types, except that
we can print random types and numbers of fields here.


The first patch adds the generic support for binary formatting.
The second adds the support for binary print types on ftrace
and the last introduces ftrace_bprintk() which supports safely the modules
by listening on the module loading/unloading notifier to keep track of
unwanted freed format strings.

Lai Jiangshan (3):
add binary printf
ftrace: infrastructure for supporting binary record
ftrace: add ftrace_bprintk()


include/asm-generic/vmlinux.lds.h | 3 +
include/linux/ftrace.h | 25 ++
include/linux/module.h | 5 +
include/linux/string.h | 7 +
kernel/module.c | 6 +
kernel/trace/Kconfig | 6 +
kernel/trace/Makefile | 1 +
kernel/trace/trace.c | 70 ++++++
kernel/trace/trace.h | 12 +
kernel/trace/trace_bprintk.c | 217 ++++++++++++++++++
kernel/trace/trace_output.c | 76 +++++++
lib/Kconfig | 3 +
lib/vsprintf.c | 442 +++++++++++++++++++++++++++++++++++++


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/