libtracecmd is a library, containing functions that can be
used without trace-cmd application. However, some of the
functions declared as libtracecmd APIs in trace-cmd.h
depend on trace-cmd context. That causes a problem when
other application uses the library. The problem can be
observed when running kerneshark and there is a python
module, loaded by the python plugin - there is a bunch
of warnings.
To resolve the problem, implementations of all trace-cmd
independent functions are moved into libtracecmd. All
libtracecmd functions, that depend on trace-cmd context
are removed from the library and from trace-cmd.h file.
Tzvetomir Stoyanov (VMware) (7):
trace-cmd: Move trace-output.c into the library code
trace-cmd: Move trace-msg.c into the library.
trace-cmd: Move trace-cmd global variable "quiet" to libtracecmd
trace-cmd: Move trace-cmd global variable "debug" to libtracecmd
trace-cmd: Move plog() function to libtracecmd.
trace-cmd: Move trace-cmd APIs from trace-cmd.h to trace-local.h
trace-cmd: Move tracecmd_stack_tracer_status() function to libtracecmd
include/trace-cmd/trace-cmd.h | 19 +-
.../include => include/trace-cmd}/trace-msg.h | 3 -
lib/trace-cmd/Makefile | 12 +-
{tracecmd => lib/trace-cmd}/trace-msg.c | 4 +-
{tracecmd => lib/trace-cmd}/trace-output.c | 4 +-
lib/trace-cmd/trace-util.c | 162 ++++++++++++++++++
tracecmd/Makefile | 2 -
tracecmd/include/trace-cmd-local.h | 2 -
tracecmd/include/trace-local.h | 14 +-
tracecmd/trace-cmd.c | 3 -
tracecmd/trace-list.c | 2 +-
tracecmd/trace-listen.c | 77 ++-------
tracecmd/trace-read.c | 8 +-
tracecmd/trace-record.c | 8 +-
tracecmd/trace-stack.c | 56 +-----
15 files changed, 221 insertions(+), 155 deletions(-)
rename {tracecmd/include => include/trace-cmd}/trace-msg.h (79%)
rename {tracecmd => lib/trace-cmd}/trace-msg.c (99%)
rename {tracecmd => lib/trace-cmd}/trace-output.c (99%)
--
2.21.0
|