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. Tzvetomir Stoyanov (VMware) (2): trace-cmd: Move kernel_stack event handler to "function" plugin. trace-cmd: Move plugin options from trace-cmd to libtraceevent. trace-cmd: Remove trace-cmd plugin handling routines include/trace-cmd/trace-cmd.h | 24 - include/traceevent/event-parse.h | 8 + kernel-shark/src/libkshark.c | 4 +- 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 | 192 +++++++- plugins/plugin_function.c | 45 +- plugins/plugin_python.c | 9 +- tracecmd/trace-check-events.c | 10 +- tracecmd/trace-list.c | 23 +- tracecmd/trace-read.c | 2 +- 12 files changed, 278 insertions(+), 856 deletions(-) -- 2.21.0
|