[RFC][PATCH 4/5] printk: Have wake_up_klogd() use __this_cpu_write()

[Steven Rostedt]

From: Steven Rostedt <srostedt@xxxxxxxxxx>

The wake up code that triggers klogd does not really matter which
CPU it enables the wake up on. Every CPU will be doing a printk_tick()
and check the current CPU. As long as one of the CPUs triggers the
wakeup we are fine. Use __this_cpu_write() instead of this_cpu_write()
to show that we do not care.

Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>
---
 kernel/printk.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/printk.c b/kernel/printk.c
index 28a40d8..e221fec 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1225,7 +1225,7 @@ int printk_needs_cpu(int cpu)
 void wake_up_klogd(void)
 {
 	if (waitqueue_active(&log_wait))
-		this_cpu_write(printk_pending, 1);
+		__this_cpu_write(printk_pending, 1);
 }
 
 /**
-- 
1.7.5.4


--
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/