On Wed, Jan 8, 2020 at 10:22 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > On Mon, 6 Jan 2020 17:40:57 +0200 > "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@xxxxxxxxx> wrote: > > > The functionality related to ftrace events and systems > > is moved from trace-cmd application and libtracecmd to libtracefs. > > > > The following libtracecmd APIs are removed: > > tracecmd_read_page_record(); > > tracecmd_event_systems(); > > tracecmd_system_events(); > > tracecmd_local_plugins(); > > tracecmd_add_list(); > > tracecmd_free_list(); > > > > The following new library APIs are introduced: > > tracefs_read_page_record(); > > tracefs_event_systems(); > > tracefs_system_events(); > > tracefs_local_plugins(); > > Hmm, we need to discuss plugins a bit more. I'm not sure they are > needed for either libtracecmd nor libtracefs. We have plugins for > libtraceevent which is just a better way to present the event, but I'm > imagining that plugins are going to be more specific to trace-cmd > directly. Maybe they can be packaged with libtracecmd, but I'm not > seeing a need for libtracefs. > > What do you have in mind? > May be the API name is confusing, it is not about the library plugins. It returns the list of plugins from "available_tracers" file. We can rename the API to tracefs_local_tracers() ? Tracers are referred as "plugins" in ftrace docs, that's why the API is named this way. > -- Steve > > > > tracefs_iterate_raw_events(); > > > > Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@xxxxxxxxx> > > --- > > -- Tzvetomir (Ceco) Stoyanov VMware Open Source Technology Center
|