Messages in this thread | | | Date | Fri, 15 Sep 2006 16:00:09 -0400 | From | Mathieu Desnoyers <> | Subject | Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 |
| |
* Andrew Morton (akpm@osdl.org) wrote: > Of course, it they are properly designed, the one set of tracepoints could > be used by different tracing backends - that allows us to separate the > concepts of "tracepoints" and "tracing backends".
If I try to develop your idea a little further, we could this of dividing the tracing problem into four layers :
- tracepoints (where the code is instrumented) - identifying code - accessing data surrounding the code - tracing backend (how to add the tracepoints) - tracing infrastructure (what code will serialize the information) - data extraction (getting the data out to disk, network, ...)
I think that, if we agree on this segmentation of the problem, this thread is generally debating on the tracing backends and their respective limitations. I just want to point out that the patch I have submitted adresses mainly the "tracing infrastructure" and "data extraction" topics.
Regards,
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |