linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v5 0/2] Remove redundant trace-cmd plugin handling logic
Date: Fri,  4 Oct 2019 18:07:04 +0300	[thread overview]
Message-ID: <20191004150706.7957-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.

All existing plugins are moved from plugins/ to lib/traceevent/plugins
directory, as all of them are designed to be used with the traceevent
library.

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.

[
  changes:
   - Removed accepted patches from the patch set.
   - Moved logic which loads traceevent development
     plugins from libtraceevent to trace-cmd application.
]

Tzvetomir Stoyanov (VMware) (2):
  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 |   3 +
 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       |  46 +++++
 lib/traceevent/event-plugin.c    |  38 ++++
 tracecmd/trace-check-events.c    |   7 +-
 tracecmd/trace-list.c            |  14 +-
 12 files changed, 538 insertions(+), 32 deletions(-)
 create mode 100644 lib/trace-cmd/plugins/Makefile
 create mode 100644 lib/trace-cmd/trace-plugin.c

-- 
2.21.0


             reply	other threads:[~2019-10-04 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 15:07 Tzvetomir Stoyanov (VMware) [this message]
2019-10-04 15:07 ` [PATCH v5 1/2] trace-cmd: Load libtraceevent plugins from build folder, if exists Tzvetomir Stoyanov (VMware)
2019-10-04 15:07 ` [PATCH v5 2/2] 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=20191004150706.7957-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).