Hi Borislav, On Fri, 15 Mar 2013 14:06:26 +0100, Borislav Petkov wrote: > From: Borislav Petkov <[email protected]> > > Yeah, > > here's a refresh of the persistent events deal, accessing those is much > cleaner now. Here's how: > > So kernel code initializes and enables the event at its convenience > (during boot, whenever) and userspace goes and says: > > sys_perf_event_open(pattr,...) > > with pattr.persistent = 1. Userspace gets the persistent buffer file > descriptor to read from. Without that, we get a normal perf file > descriptor for the duration of the tracing. > > This saves all the diddling of trying to hand down file descriptors > through debugfs or whatever. Instead, current perf code simply can use > it.
Interesting, it'll helpful profiling boot-time behaviors. So my question is how can an user know which persistent events are available in her system? Thanks, Namhyung > > This is still RFC but things are starting to fall into place slowly. As > always, any and all comments/suggestions are welcome. > > Borislav Petkov (3): > perf: Add persistent events > perf: Add persistent event facilities > MCE: Enable persistent event > > arch/x86/kernel/cpu/mcheck/mce.c | 25 +++++++ > include/linux/perf_event.h | 14 +++- > include/uapi/linux/perf_event.h | 3 +- > kernel/events/Makefile | 2 +- > kernel/events/core.c | 27 +++++--- > kernel/events/internal.h | 4 ++ > kernel/events/persistent.c | 141 > +++++++++++++++++++++++++++++++++++++++ > 7 files changed, 202 insertions(+), 14 deletions(-) > create mode 100644 kernel/events/persistent.c -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
