[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1395894625.git.tom.zanussi@linux.intel.com>
Date: Wed, 26 Mar 2014 23:54:02 -0500
From: Tom Zanussi <tom.zanussi@...ux.intel.com>
To: rostedt@...dmis.org
Cc: linux-kernel@...r.kernel.org,
Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: [PATCH 0/5] tracing: Hash triggers
Hi Steve,
This is my current code for the hash triggers mentioned in the other
thread.
I've been using it for a project here, and as such it works fine for
me, but it's nowhere near anything like a mergeable state; I'm only
sending/posting it because I didn't realize until today that you were
presenting on triggers at Collab Summit, and if as mentioned you're
thinking of adding a bullet or two for it wrt future/3.16 work, it
might be useful to have the code to play around with too...
Tom
The following changes since commit f217c44ebd41ce7369d2df07622b2839479183b0:
Merge tag 'trace-fixes-v3.14-rc7-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2014-03-26 09:09:18 -0700)
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/hashtriggers-v0
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/hashtriggers-v0
Tom Zanussi (5):
tracing: Make ftrace_event_field checking functions available
tracing: Add event record param to trigger_ops.func()
tracing: Add get_syscall_name()
tracing: Add hash trigger to Documentation
tracing: Add 'hash' event trigger command
Documentation/trace/events.txt | 81 ++
include/linux/ftrace_event.h | 8 +-
kernel/trace/trace.h | 27 +-
kernel/trace/trace_events_filter.c | 15 +-
kernel/trace/trace_events_trigger.c | 1439 ++++++++++++++++++++++++++++++++++-
kernel/trace/trace_syscalls.c | 11 +
6 files changed, 1546 insertions(+), 35 deletions(-)
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists