[GIT PULL] tracing/kprobes: Syntax updates, introduce perf probe

[Frederic Weisbecker]

Ingo,

I've tested a little this set and it seems to work well. I can't test
the C expression parser (need some libdwarf cross-version compatiblity),
but I can create kprobes via low-level parameters, then launch
perf record and perf trace successfully. I'll need to update
perf trace to handle variables that start with '$' characters though.

Anyway, it's still unstable but I guess pulling it would
help Masami to continue without the need to handle the
whole batch.

Please pull the tracing/kprobes branch that can be found at:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	tracing/kprobes

Thanks,
	Frederic.

Masami Hiramatsu (7):
      tracing/kprobes: Add $ prefix to special variables
      tracing/kprobes: Remove '$ra' special variable
      tracing/kprobes: Make special variable names more self-explainable
      tracing/kprobes: Avoid field name confliction
      tracing/kprobes: Robustify fixed field names against variable field names conflicts
      perf: Add perf probe subcommand, a kprobe-event setup helper
      perf probe: Add perf probe command support without libdwarf

 Documentation/trace/kprobetrace.txt |   27 +-
 kernel/trace/trace_kprobe.c         |  160 +++++---
 tools/perf/Makefile                 |   10 +
 tools/perf/builtin-probe.c          |  386 +++++++++++++++++++
 tools/perf/builtin.h                |    1 +
 tools/perf/perf.c                   |    1 +
 tools/perf/util/probe-finder.c      |  690 +++++++++++++++++++++++++++++++++++
 tools/perf/util/probe-finder.h      |   70 ++++
 8 files changed, 1271 insertions(+), 74 deletions(-)
 create mode 100644 tools/perf/builtin-probe.c
 create mode 100644 tools/perf/util/probe-finder.c
 create mode 100644 tools/perf/util/probe-finder.h
--
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/