From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Remove redundant trace-cmd plugin handling logic
Date: Fri, 4 Oct 2019 17:48:43 +0300 [thread overview]
Message-ID: <CAPpZLN5xoO52HNN7h8Yu8gTe+LYMh6fKp_n0r8auPNryK+aWaA@mail.gmail.com> (raw)
In-Reply-To: <20191004104648.64c42b28@gandalf.local.home>
On Fri, Oct 4, 2019 at 5:46 PM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 4 Oct 2019 16:36:42 +0300
> "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
>
> > 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.
> >
> > Tzvetomir Stoyanov (1):
> > trace-cmd: Change plugin install directories
> >
> > Tzvetomir Stoyanov (VMware) (4):
> > trace-cmd: Move libtraceevent plugins in its own directory.
> > trace-cmd: Rename plugin_python to plugin_python_loader.
> > trace-cmd: Load libtraceevent plugins from build folder, if exists.
> > trace-cmd: Add initial infrastructure for trace-cmd specific plugins.
> >
> >
>
> Hi Tzvetomir,
>
> Not sure if you noticed, but I pulled in parts of this patch series as
> they were not dependent on the patches is question.
>
> I'll take a look at the patches not yet in the series.
>
I just noticed it, going to rebase and send the next version of the
series today.
> Thanks!
>
> -- Steve
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center
prev parent reply other threads:[~2019-10-04 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 13:36 [PATCH v4 0/5] Remove redundant trace-cmd plugin handling logic Tzvetomir Stoyanov (VMware)
2019-10-04 13:36 ` [PATCH v4 1/5] trace-cmd: Move libtraceevent plugins in its own directory Tzvetomir Stoyanov (VMware)
2019-10-04 13:36 ` [PATCH v4 2/5] trace-cmd: Rename plugin_python to plugin_python_loader Tzvetomir Stoyanov (VMware)
2019-10-04 13:36 ` [PATCH v4 3/5] trace-cmd: Load libtraceevent plugins from build folder, if exists Tzvetomir Stoyanov (VMware)
2019-10-04 15:09 ` Steven Rostedt
2019-10-04 13:36 ` [PATCH v4 4/5] trace-cmd: Change plugin install directories Tzvetomir Stoyanov (VMware)
2019-10-04 13:36 ` [PATCH v4 5/5] trace-cmd: Add initial infrastructure for trace-cmd specific plugins Tzvetomir Stoyanov (VMware)
2019-10-04 14:46 ` [PATCH v4 0/5] Remove redundant trace-cmd plugin handling logic Steven Rostedt
2019-10-04 14:48 ` Tzvetomir Stoyanov [this message]
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=CAPpZLN5xoO52HNN7h8Yu8gTe+LYMh6fKp_n0r8auPNryK+aWaA@mail.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).