From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/5] tracing: Hash triggers
Date: Wed, 26 Mar 2014 23:54:02 -0500 [thread overview]
Message-ID: <cover.1395894625.git.tom.zanussi@linux.intel.com> (raw)
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
next reply other threads:[~2014-03-27 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 4:54 Tom Zanussi [this message]
2014-03-27 4:54 ` [PATCH 1/5] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2014-03-27 4:54 ` [PATCH 2/5] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2014-03-27 4:54 ` [PATCH 3/5] tracing: Add get_syscall_name() Tom Zanussi
2014-03-27 4:54 ` [PATCH 4/5] tracing: Add hash trigger to Documentation Tom Zanussi
2014-03-27 4:54 ` [PATCH 5/5] tracing: Add 'hash' event trigger command Tom Zanussi
2014-03-28 16:54 ` Andi Kleen
2014-03-28 19:13 ` Tom Zanussi
2014-04-03 8:59 ` Masami Hiramatsu
2014-04-03 22:43 ` Tom Zanussi
2014-04-04 1:44 ` Masami Hiramatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1395894625.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).