On 10/18/2010 7:34 AM, Centelles, Sylvain wrote:
Unless you know another way to have dynamic tracing/diagnostic capability
without recompiling the kernel?
there needs to be a balance.
random print's don't add diagnostic capability. well placed print's do.
if you put random dev_dbg()'s everywhere, instead you make the
diagnostic capability completely zero.
and if something is really critical, put a trace point there, not a print...
OK. That definitely makes sense, thx. Will let you know once I have the perf
impact of dynamic debug.
One of the things we may also need is related to "binary traces" (For example
to be able to trace the audio streams at the various points in the system, or complex
structure value dumps, where text traces are way too intrusive).
On other OSs, I used to have binary dumps of any structures (dynamically
controlled), with post processing to extract the structure content.
Is there a plan to have such mechanism in the kernel? Any standard API which
could be routed to PTI based logging?
see "perf" and "trace points"
we use this extensively in Linux.
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
