[patch 1/4] Markers - depends on not PREEMPT_RCU

[Mathieu Desnoyers]

Markers do not mix well with CONFIG_PREEMPT_RCU because it uses
preempt_disable/enable() and not rcu_read_lock/unlock for minimal
intrusiveness. We would need call_sched and sched_barrier primitives.

This should be in for 2.6.25.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
CC: Christoph Hellwig <hch@xxxxxxxxxxxxx>
CC: Andrew Morton <akpm@xxxxxxxx>
CC: Mike Mason <mmlnx@xxxxxxxxxx>
CC: Dipankar Sarma <dipankar@xxxxxxxxxx>
CC: David Smith <dsmith@xxxxxxxxxx>
CC: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
CC: Steven Rostedt <rostedt@xxxxxxxxxxx>
CC: Adrian Bunk <adrian.bunk@xxxxxxxxx>
---
 init/Kconfig |    1 +
 1 file changed, 1 insertion(+)

Index: linux-2.6-lttng/init/Kconfig
===================================================================
--- linux-2.6-lttng.orig/init/Kconfig	2008-03-19 18:26:47.000000000 -0400
+++ linux-2.6-lttng/init/Kconfig	2008-03-19 18:27:43.000000000 -0400
@@ -742,6 +742,7 @@ config PROFILING
 
 config MARKERS
 	bool "Activate markers"
+	depends on !PREEMPT_RCU
 	help
 	  Place an empty function call at each marker site. Can be
 	  dynamically changed for a probe function.

-- 
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/