From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/5] trace-cmd: Load libtraceevent plugins from build folder, if exists.
Date: Fri, 4 Oct 2019 11:32:11 +0300 [thread overview]
Message-ID: <CAPpZLN5ay9Jc48gy2T=0=OQ+8cQS7Z4aw4pr-mEGCBL6_-YQxw@mail.gmail.com> (raw)
In-Reply-To: <20191002194917.7563c386@gandalf.local.home>
On Thu, Oct 3, 2019 at 2:49 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 2 Oct 2019 14:41:50 +0300
> "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
>
> > When a development version of trace-cmd is built and run on the machine,
> > by default it loads only installed plugins, from system drierctories.
> > Thus, the development plugins will not be loaded. To simplify the development
> > process, a new logic is added:
> > At plugins load time, check the location of trace-cmd application and look
> > for "plugins" directory around it. If found, load plugins from it. Those
> > pluigins will be loaded last, so in case of duplication the "development"
> > plugins win.
> >
> > Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> > ---
> > lib/traceevent/event-plugin.c | 28 ++++++++++++++++++++++++++++
> > 1 file changed, 28 insertions(+)
> >
> > diff --git a/lib/traceevent/event-plugin.c b/lib/traceevent/event-plugin.c
> > index bc10205..4fc4ee3 100644
> > --- a/lib/traceevent/event-plugin.c
> > +++ b/lib/traceevent/event-plugin.c
> > @@ -14,6 +14,7 @@
> > #include <unistd.h>
> > #include <dirent.h>
> > #include <errno.h>
> > +#include <libgen.h>
> > #include "event-parse.h"
> > #include "event-parse-local.h"
> > #include "event-utils.h"
> > @@ -538,6 +539,27 @@ load_plugins_dir(struct tep_handle *tep, const char *suffix,
> > closedir(dir);
> > }
> >
> > +static char *get_source_plugins_dir(void)
> > +{
> > + char *p, path[PATH_MAX+1];
> > + int ret;
> > +
> > + ret = readlink("/proc/self/exe", path, PATH_MAX);
> > + if (ret > PATH_MAX || ret < 0)
> > + return NULL;
> > +
> > + dirname(path);
> > + p = strrchr(path, '/');
> > + if (!p)
> > + return NULL;
> > + /* Check if we are in the the source tree */
> > + if (strcmp(p, "/tracecmd") != 0)
>
> Hmm, this is in the lib/libtraceevent directory. We shouldn't be
> referencing trace-cmd code here. We should have a way to override the
> plugins from the trace-cmd side, perhaps after tep_load_plugins_hook()
> gets called?
>
I agree, we should move this check outside of the library.
I'll expose the functionality of load_plugins_dir() as a library API.
Thanks !
> -- Steve
>
>
> > + return NULL;
> > +
> > + strcpy(p, "/lib/traceevent/plugins");
> > + return strdup(path);
> > +}
> > +
> > void tep_load_plugins_hook(struct tep_handle *tep, const char *suffix,
> > void (*load_plugin)(struct tep_handle *tep,
> > const char *path,
> > @@ -588,6 +610,12 @@ void tep_load_plugins_hook(struct tep_handle *tep, const char *suffix,
> > load_plugins_dir(tep, suffix, path, load_plugin, data);
> >
> > free(path);
> > +
> > + path = get_source_plugins_dir();
> > + if (path) {
> > + load_plugins_dir(tep, suffix, path, load_plugin, data);
> > + free(path);
> > + }
> > }
> >
> > struct tep_plugin_list*
>
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center
next prev parent reply other threads:[~2019-10-04 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 11:41 [PATCH v3 0/5] Remove redundant trace-cmd plugin handling logic Tzvetomir Stoyanov (VMware)
2019-10-02 11:41 ` [PATCH v3 1/5] trace-cmd: Move libtraceevent plugins in its own directory Tzvetomir Stoyanov (VMware)
2019-10-02 11:41 ` [PATCH v3 2/5] trace-cmd: Rename plugin_python to plugin_python_loader Tzvetomir Stoyanov (VMware)
2019-10-02 11:41 ` [PATCH v3 3/5] trace-cmd: Load libtraceevent plugins from build folder, if exists Tzvetomir Stoyanov (VMware)
2019-10-02 23:49 ` Steven Rostedt
2019-10-04 8:32 ` Tzvetomir Stoyanov [this message]
2019-10-03 0:01 ` Steven Rostedt
2019-10-02 11:41 ` [PATCH v3 4/5] trace-cmd: Change plugin install directories Tzvetomir Stoyanov (VMware)
2019-10-02 11:41 ` [PATCH v3 5/5] trace-cmd: Add initial infrastructure for trace-cmd specific plugins Tzvetomir Stoyanov (VMware)
2019-10-03 0:12 ` Steven Rostedt
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='CAPpZLN5ay9Jc48gy2T=0=OQ+8cQS7Z4aw4pr-mEGCBL6_-YQxw@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).