This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108

Mathieu Desnoyers wrote:

* Ingo Molnar ( wrote:

* Roman Zippel <> wrote:

also, the other disadvantages i listed very much count too. Static tracepoints are fundamentally limited because:


Right now they are pretty heavy cons as far as LTT goes, so obviously they have a primary impact on the topic at hand (whic is whether to merge LTT or not).

Ingo, why are you arguing about static instrumentation when I don't submit any static instrumentation in my patch ? You can argue about static VS dynamic instrumentation all you want, but please don't apply this debate to a dicision about including or not a core tracing infrastructure that has nothing to do with the way instrumentation or probes are inserted.


I think Ingo is right in saying what we really need first is a generic mechanism in how to specify static markers in the kernel which can be used to put dynamic probes on demand or use as a real static function calls if one chooses. Once we agree on the marker mechanism dynamic tracing and static tracing can both co-exist happily.

Coming to your rest of the patches i really don't think we need whole lot more than the facilities we already got in the kernel. Frank has successfully demonstrated in OLS how one can use static markers by using only existing facilities in the kernel.

OpenPGP public key:
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]