[patch 0/6] Linux Kernel Markers - Use Immediate Values Optimization

[Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>]

Hi,

The Markers are meant to have a _very_ low impact on performance (even on
d-cache hits) when disabled. This is provided by the Immediate Values.

However, to be able to instrument code called from traps (NMI, MCE handler, all
code called by there functions and all traps that can be triggered by these),
the rock-solid implementation of the immediate values seems required. It,
however, comes at the cost of some added complexity.

This patch applies on 2.6.24-rc4-git3, after the 
Text Edit Lock
Immediate Values (redux)
Profiling Use Immediate Values

patchsets.

It could be interesting to queue this for 2.6.25 so we can also add basic kernel
instrumentation (patches follow).

Mathieu

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP 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 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/