[PATCH 0/4] perf tools: Persistent events, changes for perf tool integration

[Robert Richter]

From: Robert Richter <robert.richter@xxxxxxxxxxx>

This patch set contains userland changes necessary for out-of-the-box
support of persistent events. These patches are follow on patches of
the kernel patches I sent out today:

 [PATCH 00/16] perf, persistent: Kernel updates for perf tool integration

Persistent events are always enabled kernel events. Buffers are mapped
readonly and multiple users are allowed. The persistent event flag of
the event attribute must be set to specify such an event.

The following changes to perf tools are necessary to support
persistent events. A way is needed to specify sysfs entries to set
event flags. For this a new syntax 'attr<num>' was added to the event
parser, see patch #3. We also need to change perf tools to mmap
persistent event buffers readonly.

All patches can be found here:

 git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git persistent

-Robert



Robert Richter (4):
  perf tools: Rename flex conditions to avoid name conflicts
  perf tools: Modify event parser to update event attribute by index
  perf tools: Add attr<num> syntax to event parser
  perf tools: Retry mapping buffers readonly on EACCES

 tools/perf/builtin-record.c     |  7 ++++-
 tools/perf/builtin-top.c        |  8 ++++--
 tools/perf/perf.h               |  1 +
 tools/perf/tests/parse-events.c | 12 ++++++---
 tools/perf/util/parse-events.c  | 59 +++++++++++++++++++----------------------
 tools/perf/util/parse-events.h  | 12 ++++-----
 tools/perf/util/parse-events.l  | 56 +++++++++++++++++++++++---------------
 tools/perf/util/parse-events.y  | 24 ++++++++++-------
 tools/perf/util/pmu.c           | 32 +++++-----------------
 tools/perf/util/pmu.h           |  9 ++-----
 tools/perf/util/pmu.l           |  1 +
 tools/perf/util/pmu.y           | 18 ++++++++++---
 12 files changed, 127 insertions(+), 112 deletions(-)

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