Make markers use immediate values. Changelog : - Use imv_* instead of immediate_*. Signed-off-by: Mathieu Desnoyers --- Documentation/markers.txt | 17 +++++++++++++---- include/linux/marker.h | 16 ++++++++++++---- kernel/marker.c | 8 ++++++-- kernel/module.c | 1 + 4 files changed, 32 insertions(+), 10 deletions(-) Index: linux-2.6-sched-devel/include/linux/marker.h =================================================================== --- linux-2.6-sched-devel.orig/include/linux/marker.h 2008-04-24 09:17:56.000000000 -0400 +++ linux-2.6-sched-devel/include/linux/marker.h 2008-04-24 09:17:58.000000000 -0400 @@ -12,6 +12,7 @@ * See the file COPYING for more details. */ +#include #include struct module; @@ -42,7 +43,7 @@ struct marker { const char *format; /* Marker format string, describing the * variable argument list. */ - char state; /* Marker state. */ + DEFINE_IMV(char, state);/* Immediate value state. */ char ptype; /* probe type : 0 : single, 1 : multi */ /* Probe wrapper */ void (*call)(const struct marker *mdata, void *call_private, ...); @@ -74,9 +75,16 @@ struct marker { 0, 0, marker_probe_cb, \ { __mark_empty_function, NULL}, NULL }; \ __mark_check_format(format, ## args); \ - if (unlikely(__mark_##name.state)) { \ - (*__mark_##name.call) \ - (&__mark_##name, call_private, ## args);\ + if (!generic) { \ + if (unlikely(imv_read(__mark_##name.state))) \ + (*__mark_##name.call) \ + (&__mark_##name, call_private, \ + ## args); \ + } else { \ + if (unlikely(_imv_read(__mark_##name.state))) \ + (*__mark_##name.call) \ + (&__mark_##name, call_private, \ + ## args); \ } \ } while (0) Index: linux-2.6-sched-devel/kernel/marker.c =================================================================== --- linux-2.6-sched-devel.orig/kernel/marker.c 2008-04-24 09:17:56.000000000 -0400 +++ linux-2.6-sched-devel/kernel/marker.c 2008-04-24 09:17:58.000000000 -0400 @@ -23,6 +23,7 @@ #include #include #include +#include extern struct marker __start___markers[]; extern struct marker __stop___markers[]; @@ -542,7 +543,7 @@ static int set_marker(struct marker_entr */ smp_wmb(); elem->ptype = (*entry)->ptype; - elem->state = active; + elem->state__imv = active; return 0; } @@ -556,7 +557,7 @@ static int set_marker(struct marker_entr static void disable_marker(struct marker *elem) { /* leave "call" as is. It is known statically. */ - elem->state = 0; + elem->state__imv = 0; elem->single.func = __mark_empty_function; /* Update the function before setting the ptype */ smp_wmb(); @@ -620,6 +621,9 @@ static void marker_update_probes(void) marker_update_probe_range(__start___markers, __stop___markers); /* Markers in modules. */ module_update_markers(); + /* Update immediate values */ + core_imv_update(); + module_imv_update(); } /** Index: linux-2.6-sched-devel/Documentation/markers.txt =================================================================== --- linux-2.6-sched-devel.orig/Documentation/markers.txt 2008-04-24 09:17:57.000000000 -0400 +++ linux-2.6-sched-devel/Documentation/markers.txt 2008-04-24 09:17:58.000000000 -0400 @@ -15,10 +15,12 @@ provide at runtime. A marker can be "on" (no probe is attached). When a marker is "off" it has no effect, except for adding a tiny time penalty (checking a condition for a branch) and space penalty (adding a few bytes for the function call at the end of the -instrumented function and adds a data structure in a separate section). When a -marker is "on", the function you provide is called each time the marker is -executed, in the execution context of the caller. When the function provided -ends its execution, it returns to the caller (continuing from the marker site). +instrumented function and adds a data structure in a separate section). The +immediate values are used to minimize the impact on data cache, encoding the +condition in the instruction stream. When a marker is "on", the function you +provide is called each time the marker is executed, in the execution context of +the caller. When the function provided ends its execution, it returns to the +caller (continuing from the marker site). You can put markers at important locations in the code. Markers are lightweight hooks that can pass an arbitrary number of parameters, @@ -69,6 +71,13 @@ a printk warning which identifies the in "Format mismatch for probe probe_name (format), marker (format)" +* Optimization for a given architecture + +To force use of a non-optimized version of the markers, _trace_mark() should be +used. It takes the same parameters as the normal markers, but it does not use +the immediate values based on code patching. + + * Probe / marker example See the example provided in samples/markers/src Index: linux-2.6-sched-devel/kernel/module.c =================================================================== --- linux-2.6-sched-devel.orig/kernel/module.c 2008-04-24 09:17:56.000000000 -0400 +++ linux-2.6-sched-devel/kernel/module.c 2008-04-24 09:17:58.000000000 -0400 @@ -2052,6 +2052,7 @@ static struct module *load_module(void _ mod->markers + mod->num_markers); #endif #ifdef CONFIG_IMMEDIATE + /* Immediate values must be updated after markers */ imv_update_range(mod->immediate, mod->immediate + mod->num_immediate); #endif -- 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/