Hi - On Fri, Mar 28, 2008 at 03:41:16PM +0100, Ingo Molnar wrote:This complaint is particularly rich, seeing how you constantly try to shoot down patches that would reduce systemtap's need for this, such as markers. And no, dyn-ftrace is not a complete substitute. See how many of the markers in mathieu's lttng suite occur at places *other* than function entry points. See how many require parameters other than what may already sit in registers. We in systemtap land have always had to make do with whatever was in the kernel. There was very little other than kprobes 3 years ago. Of newer facilities such as markers, ftrace, perfmon2 (I hope), and a bunch of other little tracer thingies, all those that provide a usable callback style interface can be exposed to systemtap. The more the merrier, and the less we'd have to resort to the lowest-level kprobes/dwarf stuff. Please help rather than obstruct. - FChE --
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
