Messages in this thread | | | Date | Thu, 14 Sep 2006 14:38:25 -0400 | From | Karim Yaghmour <> | Subject | Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 |
| |
Nick Piggin wrote: > What's the huge problem with making kprobes the only option (that can't > be fixed by doing a bit of coding)?
No offense, having been on the receiving end of this for a number of years, one feels like he's watching a never-ending repeat of a 30second commercial where the woman is holding up a magic scrub and says something like "Just use Mr. Scrub" and the product then twinkles with some light music and then cut, next commercial; except in this case, it's "Just use Kprobes" and all your problems will go away, wink-wink!
Sorry, it's just not that straight-forward. There's a reason why the systemtap folks got interested in the markers proposal, they actually have to maintain a dynamic instrumentation set. Mr. Scrub just doesn't scrub as clean as advertised, you actually have to scrub to make the scum go away. Which goes back to what I said elsewhere: no matter where you draw the line someone is doing the heavy lifting. Doing it outside the kernel only means that there's yet another piece of software that needs to be updated before you can actually start profiting from your new and improved kernel ...
Karim
- 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/
| |