From: David Ahern <dsahern@gmail.com>
To: rostedt@goodmis.org, acme@ghostprotocols.net,
linux-kernel@vger.kernel.org, weisbec@gmail.com
Cc: namhyung.kim@lge.com, mingo@kernel.org, peterz@infradead.org,
David Ahern <dsahern@gmail.com>
Subject: [RFC PATCH 0/2] libtraceevent/perf: Add support for trace-cmd plugins
Date: Thu, 14 Jun 2012 11:35:31 -0600 [thread overview]
Message-ID: <1339695333-64591-1-git-send-email-dsahern@gmail.com> (raw)
Now that perf is using libtraceevent and libtraceevent is based
on trace-cmd both can be extended to leverage the plugins written
for trace-cmd to improve pretty printing of the events.
Given that it is based on code from trace-cmd I am not sure what the
right approach is, so wanted to throw this out for comments/suggestions.
David Ahern (2):
libtraceevent: Add support for tracecmd plugins
perf: add support for trace-cmd plugins
tools/lib/traceevent/Makefile | 2 +-
tools/lib/traceevent/tracecmd-plugins.c | 280 +++++++++++++++++++++++++++++++
tools/lib/traceevent/tracecmd-plugins.h | 34 ++++
tools/perf/util/trace-event-parse.c | 4 +
4 files changed, 319 insertions(+), 1 deletion(-)
create mode 100644 tools/lib/traceevent/tracecmd-plugins.c
create mode 100644 tools/lib/traceevent/tracecmd-plugins.h
--
1.7.10.1
next reply other threads:[~2012-06-14 17:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 17:35 David Ahern [this message]
2012-06-14 17:35 ` [RFC PATCH 1/2] libtraceevent: Add support for tracecmd plugins David Ahern
2012-06-14 17:35 ` [RFC PATCH 2/2] perf: add support for trace-cmd plugins David Ahern
2012-06-18 8:35 ` [RFC PATCH 0/2] libtraceevent/perf: Add " Namhyung Kim
2012-06-18 14:21 ` Steven Rostedt
2012-06-18 14:35 ` David Ahern
2012-06-18 14:38 ` David Ahern
2012-06-19 0:45 ` Namhyung Kim
2012-06-19 1:03 ` Steven Rostedt
2012-06-19 1:11 ` Namhyung Kim
2012-06-19 1:26 ` Steven Rostedt
2012-06-19 1:40 ` Namhyung Kim
2012-06-19 2:16 ` Steven Rostedt
2012-06-19 5:41 ` Namhyung Kim
2012-06-19 11:54 ` Steven Rostedt
2012-06-19 14:39 ` Namhyung Kim
2012-06-19 14:44 ` Steven Rostedt
2012-06-19 1:14 ` David Ahern
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=1339695333-64591-1-git-send-email-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=weisbec@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.