[RFC PATCH -v2 0/4] Persistent events

[Borislav Petkov]

From: Borislav Petkov <borislav.petkov@xxxxxxx>

Hi all,

off and on I get some free time to work on that, here's the latest
incarnation. It contains review feedback from the earlier round.

Patch 1/4 adds a trace_add_file() interface which adds an additional
file to debugfs, in this case the "persistent" file which contains the
normal perf file descriptor sys_perf_event_open gives to the perf tool.

IOW, one gets:

/mnt/dbg/tracing/events/mce/mce_record/
|-- enable
|-- filter
|-- format
|-- id
`-- persistent1

0 directories, 5 files

 [ 1 is the CPU number so sticking all per-CPU descriptors in this
 directory could get a little cluttered and ugly so I'll have to think
 about that a bit more. ]

3/4 is the meat which adds <kernel/events/persistent.c> and 4/4 shows
how one can init a persistent event on a CPU.

What remains is adding code which can enable events on boot from the
kernel cmdline and more testing.

As always, comments and suggestions are appreciated.

Thanks.

Borislav Petkov (4):
  trace events: Interface to add files to debugfs
  perf: Add persistent events
  perf: Add persistent event facilities
  persistent test

 arch/x86/include/asm/mce.h       |   1 +
 arch/x86/kernel/cpu/mcheck/mce.c |   5 ++
 include/linux/ftrace_event.h     |   3 +
 include/linux/perf_event.h       |  24 +++++-
 kernel/events/Makefile           |   2 +-
 kernel/events/core.c             |  18 +++--
 kernel/events/internal.h         |   2 +
 kernel/events/persistent.c       | 168 +++++++++++++++++++++++++++++++++++++++
 kernel/trace/trace.c             |   4 +
 kernel/trace/trace.h             |   1 +
 kernel/trace/trace_events.c      |  35 ++++++++
 11 files changed, 254 insertions(+), 9 deletions(-)
 create mode 100644 kernel/events/persistent.c

-- 
1.7.11.rc1

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