On Fri, Oct 4, 2019 at 5:46 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > On Fri, 4 Oct 2019 16:36:42 +0300 > "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@xxxxxxxxx> 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
|