From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/3] Remove redundant trace-cmd plugin handling logic
Date: Fri, 26 Jul 2019 15:43:05 +0300 [thread overview]
Message-ID: <20190726124308.18735-1-tz.stoyanov@gmail.com> (raw)
Currently there are no trace-cmd related plugins, all of them
are designed to be used with libtraceeevnt. As both libtraceevent
and trace-cmd have logic for managing plugins, the one in trace-cmd
is redundant. Those redundant code is removed and replaced with calls
to libtraceeevnt plugin APIs. When trace-cmd has to load any plugins,
it uses libtraceeevnt to do the job.
Tzvetomir Stoyanov (VMware) (2):
trace-cmd: Move kernel_stack event handler to "function" plugin.
trace-cmd: Move plugin options from trace-cmd to libtraceevent.
trace-cmd: Remove trace-cmd plugin handling routines
include/trace-cmd/trace-cmd.h | 24 -
include/traceevent/event-parse.h | 8 +
kernel-shark/src/libkshark.c | 4 +-
lib/trace-cmd/trace-ftrace.c | 56 +--
lib/trace-cmd/trace-input.c | 9 +-
lib/trace-cmd/trace-util.c | 752 +------------------------------
lib/traceevent/event-plugin.c | 192 +++++++-
plugins/plugin_function.c | 45 +-
plugins/plugin_python.c | 9 +-
tracecmd/trace-check-events.c | 10 +-
tracecmd/trace-list.c | 23 +-
tracecmd/trace-read.c | 2 +-
12 files changed, 278 insertions(+), 856 deletions(-)
--
2.21.0
next reply other threads:[~2019-07-26 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 12:43 Tzvetomir Stoyanov (VMware) [this message]
2019-07-26 12:43 ` [PATCH 1/3] trace-cmd: Move kernel_stack event handler to "function" plugin Tzvetomir Stoyanov (VMware)
2019-07-26 12:43 ` [PATCH 2/3] trace-cmd: Move plugin options from trace-cmd to libtraceevent Tzvetomir Stoyanov (VMware)
2019-07-29 17:01 ` Steven Rostedt
2019-07-26 12:43 ` [PATCH 3/3] trace-cmd: Remove trace-cmd plugin handling routines Tzvetomir Stoyanov (VMware)
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=20190726124308.18735-1-tz.stoyanov@gmail.com \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@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).