Messages in this thread | | | Date | Fri, 15 Sep 2006 18:32:27 -0400 | From | Karim Yaghmour <> | Subject | Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108 |
| |
Ingo Molnar wrote: > that is not true at all. Yes, an INT3 based kprobe might be expensive if > +0.5 usecs per tracepoint (on a 1GHz CPU) is an issue to you - but that > is "only" an implementation detail, not a conceptual property. > Especially considering that help (djprobes) is on the way. And in the
djprobes has been "on the way" for some time now. Why don't you at least have the intellectual honesty to use the same rules you've repeatedly used against ltt elsewhere in this thread -- i.e. what it does today is what it is, and what it does today isn't worth bragging about. But that would be too much to ask of you Ingo, wouldn't it?
But, sarcasm aside, even if this mechanism existed it still wouldn't resolve the need for static markup. It would just make djprobe a likelier candidate for tools that cannot currently rely on kprobes.
> NOTE: i still accept the temporary (or non-temporary) introduction of > static markers, to help dynamic tracing. But my expectation is that > these markers will be less intrusive than static tracepoints, and a lot > more flexible.
Chalk one up for nice endorsement and another for arbitrary distinction.
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/
| |