Messages in this thread | | | Date | Mon, 10 Oct 2011 16:21:27 +0200 | From | Frederic Weisbecker <> | Subject | Re: [PATCHv2 1/2] perf tools: Collect tracing event data files directly |
| |
On Mon, Oct 10, 2011 at 08:27:34AM -0400, Steven Rostedt wrote: > > Please work out disagreements with Arnaldo and do librarization > > within perf if you are interested in that angle. If those internal > > interfaces become visibly boring and are consistently used by > > everything in a way that every main contributor agrees on then we can > > perhaps librarize it. Not the other way around. > > For parsing of events, which is what I proposed, it seems to be boring > technical stuff that has been well established by the limitations of the > ABI forced on the debugfs system. It's already over a year old and used > by several developers. One nice feature to come with this is the ability > to add plugins to parse the trace events without needing to read all the > format files. Things like kvm events will suddenly work. > > The one disagreement that we are still sorting out is just the name of > the library. I first said libperf (which would make sense to have in > tools/perf/lib) but then it wasn't doing perf specific work. It was just > a way to parse kernel trace points. Nobody seemed to like libparsevent. > I think one of the names that makes sense is libtrace, or libktrace as > it has to do with tracepoints in the kernel. Maybe just libktracepoint? > But that's quite an ugly name.
libtracevent ?
| |