Cc: Ingo Oeser <ioe-lkml@...>, Paul Jackson <pj@...>, <linux-kernel@...>, Con Kolivas <kernel@...>, Derek L. Fults <dfults@...>, devik <devik@...>, Dimitri Sivanich <sivanich@...>, Dinakar Guniguntala <dino@...>, Emmanuel Pacaud <emmanuel.pacaud@...>, Frederik Deweerdt <deweerdt@...>, Ingo Molnar <mingo@...>, Matthew Dobson <colpatch@...>, Nick Piggin <nickpiggin@...>, <rostedt@...>, Oleg Nesterov <oleg@...>, Paul E. McKenney <paulmck@...>, Paul Menage <menage@...>, Randy.Dunlap <rddunlap@...>, <suresh.b.siddha@...>, Thomas Gleixner <tglx@...>
Ingo, I just wanted to elaborate on what Peter is saying. That CPU will still
have to be _booted_ properly. It may be used for hard- and soft- interrupt
processing, workqueues (internal kernel queuing mechanism) and kernel timers.
In your particular case you're much much much better off with doing
echo 0 > /sys/devices/system/cpuN/online
either during initrd stage or as a first init script.
That way bad cpu will be _completely_ disabled.
Max
--
