* Linus Torvalds (torvalds@xxxxxxxxxxxxxxxxxxxx) wrote: > > > On Fri, 25 Apr 2008, Mathieu Desnoyers wrote: > > > > DWARF2 is capable of extracting information only when not optimized away > > by the compiler. That's the whole point of markers : liveness is good in > > this case because we make sure the variable is there, not that it > > *might* be there. The latter case might be good enough for a debugger, > > but not for a production system tracer. > > This is why you really do want to recompile the function entirely if > you're debugging it. Because it might simply not be debuggable in its > normal state. > > I'd much rather see something truly generic that doesn't need any > pre-inserted "markers" at all that disable optimizations, and that allows Markers, with immediate values, only clobbers the eax register and the ZF. It does not restrain inlining nor loop unrolling. It also requires gcc to leave the variables in which the marker is interested "live". Are you referring to other optimizations I wouldn't have though of ? > just about anything. Including live system bug-fixes etc (imagine finding > a bug - and not at somethign that was previously already "marked" - and > just replacing the buggy function with a non-buggy one). > > Linus kprobes is already doing a good job at probing a live system without rebooting. Markers are best suited to export information about kernel events which stays stable between releases so the information is readily available in the kernel, with low overhead even when tracing is enabled (which kprobes doesn't provide) which allows a user to flip the "on" switch and get a trace of all system calls, scheduling, traps, interrupts that happen on the system. Mathieu -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
