Satoru Takeuchi 85653af7d4 Fix stop_machine_run problem with naughty real time process
stop_machine_run() does its work on "kstopmachine" thread having max
priority.  However that thread get such priority after woken up.
Therefore, in the following case ...

  - "kstopmachine" try to run on CPU1

  - There is a real time process which doesn't relinquish CPU time
    voluntary on CPU1

...  "kstopmachine" can't start to run and the CPU on which
    stop_machine_run() is runing hangs up.  To fix this problem, call
    sched_setscheduler() before waking up that thread.

Signed-off-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Ashok Raj <ashok.raj@intel.com>
Cc: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-16 09:05:41 -07:00
..
2007-07-16 09:05:41 -07:00
2007-05-11 05:38:25 -04:00
2007-05-11 05:38:26 -04:00
2007-06-24 12:08:53 -07:00
2006-12-07 08:39:36 -08:00
2006-12-04 02:00:22 -05:00
2007-05-09 12:30:56 -07:00
2007-05-21 09:18:19 -07:00
2007-07-13 14:14:28 +02:00
2007-07-09 18:51:58 +02:00
2005-04-16 15:20:36 -07:00
2007-05-11 08:29:35 -07:00
2006-12-07 08:39:25 -08:00
2007-05-09 08:57:56 +02:00