On Mon, 07 May 2007 19:10:05 +0900 Satoru Takeuchi <[EMAIL PROTECTED]> wrote:
> kstopmachine is created, bound to the CPU1, and woken up here, but > this process can't start to run because reschedule doesn't occur on > CPU1. Hence CPU0 also be able to run because it's waiting completion > of CPU1's offline work. > Is this Bug ? It seems the system works as designed... Hmm, adding stop_machine_run_interruptible() and using wait_for_completion_interruptible() instead of wait_for_completion() is O.K. ? Then we can stop cpu hot-unplug by signal. Is this okay for you ? -Kame - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
