From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v6 0/3] Remove redundant trace-cmd plugin handling logic
Date: Mon, 7 Oct 2019 14:49:44 +0300 [thread overview]
Message-ID: <20191007114947.17104-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.
A new libtraceevent API is introduced, which can be used to define
custom plugin directories. It is used by trace-cmd to load development
plugins, if any.
An initial infrastructure for trace-cmd specific plugins is added -
new lib/trace-cmd/plugins directory and an initial set of APIs
for working with trace-cmd plugins.
[
v6 changes:
- Introduced new libtraceevent API for adding custom plugin directories.
v5 changes:
- Removed accepted patches from the patch set.
- Moved logic which loads traceevent development
plugins from libtraceevent to trace-cmd application.
]
Tzvetomir Stoyanov (VMware) (3):
trace-cmd: Introduced new traceevent API, for adding new plugins
directories.
trace-cmd: Load libtraceevent plugins from build folder, if exists.
trace-cmd: Add initial infrastructure for trace-cmd specific plugins.
.gitignore | 1 +
Makefile | 40 +++-
include/trace-cmd/trace-cmd.h | 42 ++++
include/traceevent/event-parse.h | 7 +
lib/trace-cmd/Makefile | 1 +
lib/trace-cmd/plugins/Makefile | 58 ++++++
lib/trace-cmd/trace-input.c | 7 +-
lib/trace-cmd/trace-plugin.c | 313 +++++++++++++++++++++++++++++
lib/trace-cmd/trace-util.c | 42 ++++
lib/traceevent/event-parse-local.h | 5 +-
lib/traceevent/event-parse.c | 1 +
lib/traceevent/event-plugin.c | 70 +++++++
tracecmd/trace-check-events.c | 7 +-
tracecmd/trace-list.c | 14 +-
14 files changed, 575 insertions(+), 33 deletions(-)
create mode 100644 lib/trace-cmd/plugins/Makefile
create mode 100644 lib/trace-cmd/trace-plugin.c
--
2.21.0
next reply other threads:[~2019-10-07 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 11:49 Tzvetomir Stoyanov (VMware) [this message]
2019-10-07 11:49 ` [PATCH v6 1/3] trace-cmd: Introduced new traceevent API, for adding new plugins directories Tzvetomir Stoyanov (VMware)
2019-10-07 11:49 ` [PATCH v6 2/3] trace-cmd: Load libtraceevent plugins from build folder, if exists Tzvetomir Stoyanov (VMware)
2019-12-02 7:54 ` Tzvetomir Stoyanov
2019-12-02 21:19 ` Steven Rostedt
2019-10-07 11:49 ` [PATCH v6 3/3] trace-cmd: Add initial infrastructure for trace-cmd specific plugins 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=20191007114947.17104-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 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.