[PATCH RT] Don't allow non-threaded softirqs and threaded hardirqs

[Steven Rostedt <rostedt@goodmis.org>]

Ingo,

I think this was sent before, and it did cause problems before. Would
there be *any* reason to have non-threaded softirqs but threaded hardirqs.
I can see lots of issues with that.

This patch has selecting hardirqs also select softirqs as threads.

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

Index: linux-2.6.21.5-rt18/kernel/Kconfig.preempt
===================================================================
--- linux-2.6.21.5-rt18.orig/kernel/Kconfig.preempt	2007-06-28 16:58:49.000000000 -0400
+++ linux-2.6.21.5-rt18/kernel/Kconfig.preempt	2007-06-28 17:00:07.000000000 -0400
@@ -106,6 +106,7 @@ config PREEMPT_HARDIRQS
 	bool "Thread Hardirqs"
 	default n
 	depends on !GENERIC_HARDIRQS_NO__DO_IRQ
+	select PREEMPT_SOFTIRQS
 	help
 	  This option reduces the latency of the kernel by 'threading'
           hardirqs. This means that all (or selected) hardirqs will run
-
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/