Re: [PATCH 0/8] [GIT PULL] simplify the print fmt in the eventformat files

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> Ingo,
> 
> Changes since my RFC:
> 
>  - Rebased against my last tip/tracing/ftrace push
>  - Added ifmask and uint (will be adding more tags soon)
>  - Added memory clean up on error
>  - Added locking for module unload
>  - Added memory clean up of formats on module unload
>  - Added lockdep update
>  - Add entry size to iterator (will be used soon)
> 
> Please pull the latest tip/tracing/event-print-format tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/event-print-format
> 
> 
> Steven Rostedt (8):
>       tracing: add trace_seq_vprint interface
>       tracing: add protection around module events unload
>       tracing/events: nicer print format for parsing
>       tracing/events: modify irq print to new format
>       tracing/events: modify sched print to new format
>       tracing/events: modify kmem print to new format
>       tracing/events: modify lockdep print to new format
>       tracing: add entry size to iterator
> 
> ----
>  include/linux/ftrace_event.h     |   12 +
>  include/linux/trace_seq.h        |    2 +
>  include/trace/events/irq.h       |   38 +-
>  include/trace/events/kmem.h      |   98 +++---
>  include/trace/events/lockdep.h   |   12 +-
>  include/trace/events/sched.h     |   49 +--
>  include/trace/ftrace.h           |   22 +-
>  kernel/trace/Makefile            |    1 +
>  kernel/trace/trace.c             |   39 ++-
>  kernel/trace/trace_events.c      |    5 +-
>  kernel/trace/trace_output.c      |   47 +++-
>  kernel/trace/trace_output.h      |    4 +
>  kernel/trace/trace_read_binary.c |  766 ++++++++++++++++++++++++++++++++++++++
>  13 files changed, 962 insertions(+), 133 deletions(-)

This looks quite nice - albeit a bit large so late. I've pulled it, 
hopefully it tests fine :)

	Ingo
--
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/