From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/7] trace-cmd,libtraceevent: Rework of plugin options APIs
Date: Wed, 22 Jan 2020 16:59:55 +0200 [thread overview]
Message-ID: <20200122150002.763233-1-tz.stoyanov@gmail.com> (raw)
In order to simplify libtracevents APIs, logic related to plugins and
plugin options is reworked:
- Complex and not used APIs are removed.
- Logic for printing various information for plugins and plugin options
is moved from the library to the application.
- Additional checks are added when loading new plugins and options, to
avoid duplications.
Tzvetomir Stoyanov (VMware) (7):
trace-cmd,libtraceevent: Plugin options rework
trace-cmd,libtraceevent: Remove TEP_PLUGIN_OPTIONS
trace-cmd,libtraceevent: Check for plugin options duplication
trace-cmd,libtraceevent: Check for plugin duplication
trace-cmd,libtraceevent: Remove API for plugin options print
trace-cmd,libtraceevent: Remove API for plugin print
trace-cmd, kernelshark, libtraceevent: Changed tep_plugin_add_option()
API
include/traceevent/event-parse.h | 50 +---
kernel-shark/src/libkshark.c | 4 +-
lib/trace-cmd/trace-ftrace.c | 4 +-
lib/trace-cmd/trace-plugin.c | 5 -
lib/traceevent/event-plugin.c | 279 ++++++++++-------------
lib/traceevent/plugins/plugin_function.c | 6 +-
tracecmd/trace-list.c | 55 ++++-
tracecmd/trace-read.c | 2 +-
8 files changed, 188 insertions(+), 217 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-22 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 14:59 Tzvetomir Stoyanov (VMware) [this message]
2020-01-22 14:59 ` [PATCH 1/7] trace-cmd,libtraceevent: Plugin options rework Tzvetomir Stoyanov (VMware)
2020-01-22 14:59 ` [PATCH 2/7] trace-cmd,libtraceevent: Remove TEP_PLUGIN_OPTIONS Tzvetomir Stoyanov (VMware)
2020-01-22 14:59 ` [PATCH 3/7] trace-cmd,libtraceevent: Check for plugin options duplication Tzvetomir Stoyanov (VMware)
2020-01-22 14:59 ` [PATCH 4/7] trace-cmd,libtraceevent: Check for plugin duplication Tzvetomir Stoyanov (VMware)
2020-01-22 15:00 ` [PATCH 5/7] trace-cmd,libtraceevent: Remove API for plugin options print Tzvetomir Stoyanov (VMware)
2020-01-22 15:00 ` [PATCH 6/7] trace-cmd,libtraceevent: Remove API for plugin print Tzvetomir Stoyanov (VMware)
2020-01-22 15:00 ` [PATCH 7/7] trace-cmd, kernelshark, libtraceevent: Changed tep_plugin_add_option() API 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=20200122150002.763233-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).