* Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> wrote: > Hi Ingo, > > * Ingo Molnar (mingo@xxxxxxx) wrote: > [...] > > Mathieu, please work with the tracing folks who DO care about > > this stuff. It's not like there's a lack of interest in this > > area, nor is there a lack of willingness to take patches. What > > there is a lack of is your willingness to actually work on > > getting something unified, integrated to users... > > > > LTTNG has been going on for how many years? I havent seen many > > steps towards actually *merging* its functionality - you insist > > on doing your own random thing, which is different in random > > ways. Yes, some of those random ways may in fact be better than > > what we have upstream - would you be interested in filtering > > those out and pushing them upstream? I certainly would like to > > see that happen. > > > > We want to pick the best features, and throw away current > > upstream code in favor of superior out of tree code - this > > concept of letting crap sit alongside each other when people do > > care i cannot agree with. > > LTTng 2.0, today, offers a unified interface for kernel and > userspace tracing, in the form of libraries and git-alike > command line user interface. [...] Note that Arnaldo is working on such a perf-alike tracing tool workflow with the new 'trace' utility that we announced and prototyped a couple of months ago. The perf.data data format is now extensible as well and tightened for transportability. Tools such as PowerTop or sysprof have standardized around the perf ABI. So there's a *lot* of overlap with existing upstream efforts and the last thing we need is the parallel LTTNG ABI. Are you willing to merge LTTNG into our existing kernel and userspace infrastructure and ABIs, with the possible end result that LTTNG ceases to be a separately named entity? Mind hooking up with Arnaldo and with Steve regarding how we could best split up the LTTNG bits and move them upstream? Frankly, i've seen a *lot* of talk from you but unfortunately *very* little action on that front, so i think my healthy scepticism is justified. Thanks, Ingo _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
