[PATCH 00/22] perf tools: Backport of latest changes on trace-cmd's libparseevent

From: Namhyung Kim
Date: Tue May 22 2012 - 22:44:40 EST


Hi,

This is a patchset which attempts to sync what we have on trace-cmd
into libtraceevent. Although some patch introduced new call-sites of
die() or malloc_or_die(), it'll be removed eventually (or later work)
and this helps marking the every locations that we need to track.

Thanks,
Namhyung


Namhyung Kim (15):
lib/traceevent: Fix printk_cmp()
lib/traceevent: Introduce extend_token()
lib/traceevent: Handle strdup failure cases
lib/traceevent: Fix a possible memory leak
lib/traceevent: Handle realloc() failure path
lib/traceevent: Fix a possibly wrong memory dereference
lib/traceevent: Fix freeing arg on process_dynamic_array()
lib/traceevent: Use proper function parameter type
lib/traceevent: Pass string type argument to args
lib/traceevent: Do not call add_event() again if allocation failed
lib/traceevent: Fix some comments
lib/traceevent: Check result of malloc() during reading token
lib/traceevent: Fix signature of create_arg_item()
lib/traceevent: Check return value of arg_to_str()
lib/traceevent: Cleanup realloc use

Peter Huewe (1):
lib/traceevent: Add missing break in make_bprint_args

Stefan Hajnoczi (1):
lib/traceevent: Allow expressions in __print_symbolic() fields

Steven Rostedt (4):
lib/traceevent: Let filtering numbers by string use function names
lib/traceevent: Add support for "%.*s" in bprintk events
lib/traceevent: Add support to show migrate disable counter
lib/traceevent: Fix %pM print format arg handling

Wolfgang Mauerer (1):
lib/traceevent: Fix trace_printk for long integers

tools/lib/traceevent/event-parse.c | 309 ++++++++++++++++++++++++-----------
tools/lib/traceevent/parse-filter.c | 91 +++++++----
2 files changed, 271 insertions(+), 129 deletions(-)

--
1.7.10.1

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