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 v2 0/6] Remove redundant trace-cmd plugin handling logic
Date: Fri,  2 Aug 2019 14:00:55 +0300	[thread overview]
Message-ID: <20190802110101.14759-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 plugins/traceevent/
directory, as all of them (except plugin_python) are designed to be
used with the traceevent library. This change paves the way for
implementing trace-cmd specific plugins.

Tzvetomir  Stoyanov (VMware) (1):
  trace-cmd: Remove trace-cmd plugin handling routines

Tzvetomir Stoyanov (1):
  trace-cmd: Change plugin install directories

Tzvetomir Stoyanov (VMware) (4):
  trace-cmd: Move kernel_stack event handler to "function" plugin.
  trace-cmd: Move plugin options from trace-cmd to libtraceevent.
  trace-cmd: Move libtraceevent plugins in its own directory.
  trace-cmd: Load libtraceevent plugins from build folder, if exists.

 .gitignore                                    |   2 +-
 Makefile                                      |  44 +-
 include/trace-cmd/trace-cmd.h                 |  24 -
 include/traceevent/event-parse.h              |   8 +
 kernel-shark/src/libkshark.c                  |   4 +-
 lib/trace-cmd/Makefile                        |   2 -
 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                 | 226 +++++-
 plugins/{ => traceevent}/Makefile             |  12 +-
 plugins/{ => traceevent}/plugin_blk.c         |   0
 plugins/{ => traceevent}/plugin_cfg80211.c    |   0
 plugins/{ => traceevent}/plugin_function.c    |  45 +-
 plugins/{ => traceevent}/plugin_futex.c       |   0
 plugins/{ => traceevent}/plugin_hrtimer.c     |   0
 plugins/{ => traceevent}/plugin_jbd2.c        |   0
 plugins/{ => traceevent}/plugin_kmem.c        |   0
 plugins/{ => traceevent}/plugin_kvm.c         |   0
 plugins/{ => traceevent}/plugin_mac80211.c    |   0
 plugins/{ => traceevent}/plugin_python.c      |   9 +-
 .../{ => traceevent}/plugin_sched_switch.c    |   0
 plugins/{ => traceevent}/plugin_scsi.c        |   0
 plugins/{ => traceevent}/plugin_tlb.c         |   0
 plugins/{ => traceevent}/plugin_xen.c         |   0
 tracecmd/trace-check-events.c                 |  10 +-
 tracecmd/trace-list.c                         |  23 +-
 tracecmd/trace-read.c                         |   2 +-
 28 files changed, 338 insertions(+), 890 deletions(-)
 rename plugins/{ => traceevent}/Makefile (86%)
 rename plugins/{ => traceevent}/plugin_blk.c (100%)
 rename plugins/{ => traceevent}/plugin_cfg80211.c (100%)
 rename plugins/{ => traceevent}/plugin_function.c (79%)
 rename plugins/{ => traceevent}/plugin_futex.c (100%)
 rename plugins/{ => traceevent}/plugin_hrtimer.c (100%)
 rename plugins/{ => traceevent}/plugin_jbd2.c (100%)
 rename plugins/{ => traceevent}/plugin_kmem.c (100%)
 rename plugins/{ => traceevent}/plugin_kvm.c (100%)
 rename plugins/{ => traceevent}/plugin_mac80211.c (100%)
 rename plugins/{ => traceevent}/plugin_python.c (91%)
 rename plugins/{ => traceevent}/plugin_sched_switch.c (100%)
 rename plugins/{ => traceevent}/plugin_scsi.c (100%)
 rename plugins/{ => traceevent}/plugin_tlb.c (100%)
 rename plugins/{ => traceevent}/plugin_xen.c (100%)

-- 
2.21.0


             reply	other threads:[~2019-08-02 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 11:00 Tzvetomir Stoyanov (VMware) [this message]
2019-08-02 11:00 ` [PATCH v2 1/6] trace-cmd: Move kernel_stack event handler to "function" plugin Tzvetomir Stoyanov (VMware)
2019-08-02 11:00 ` [PATCH v2 2/6] trace-cmd: Move plugin options from trace-cmd to libtraceevent Tzvetomir Stoyanov (VMware)
2019-08-02 11:00 ` [PATCH v2 3/6] trace-cmd: Remove trace-cmd plugin handling routines Tzvetomir Stoyanov (VMware)
2019-08-02 11:00 ` [PATCH v2 4/6] trace-cmd: Move libtraceevent plugins in its own directory Tzvetomir Stoyanov (VMware)
2019-08-30 15:23   ` Steven Rostedt
2019-08-02 11:01 ` [PATCH v2 5/6] trace-cmd: Load libtraceevent plugins from build folder, if exists Tzvetomir Stoyanov (VMware)
2019-08-02 11:01 ` [PATCH v2 6/6] trace-cmd: Change plugin install directories 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=20190802110101.14759-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).