Message ID | 20190814084712.28188-1-tz.stoyanov@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Separate trace-cmd and libtracecmd code | expand |
On Wed, 14 Aug 2019 11:47:00 +0300 "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote: > libtracecmd is a library, containing functions that can be > used without the 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. > I pulled in some but not all of these patches (the ones I had comments on). Feel free to rebase on the git repo and you only need to send the ones that have not been applied. -- Steve