{"shas":[["162da47c45f731ed055f9a7499530793e96b4557","90e2dfd4673a6805c78e66cea432ef966f1a9d64@in.ibm.com","sched: kill migration thread in CPU_POST_DEAD instead of CPU_DEAD\n\n[Fixed in a different manner upstream, due to rewrites in this area]\n\nProblem : In a stress test where some heavy tests were running along with\nregular CPU offlining and onlining, a hang was observed. The system seems to\nbe hung at a point where migration_call() tries to kill the migration_thread\nof the dying CPU, which just got moved to the current CPU. This migration\nthread does not get a chance to run (and die) since rt_throttled is set to 1\non current, and it doesn't get cleared as the hrtimer which is supposed to\nreset the rt bandwidth (sched_rt_period_timer) is tied to the CPU which we just\nmarked dead!\n\nSolution : This patch pushes the killing of migration thread to \"CPU_POST_DEAD\"\nevent. By then all the timers (including sched_rt_period_timer) should have got\nmigrated (along with other callbacks).\n\nSigned-off-by: Amit Arora <amitarora@in.ibm.com>\nSigned-off-by: Gautham R Shenoy <ego@in.ibm.com>\nSigned-off-by: Mike Galbraith <efault@gmx.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@suse.de>","Amit Arora"]],"repo":"adrynalyne/kernel_htc-mecha","actor":"adrynalyne","ref":"refs/heads/master","size":1,"head":"162da47c45f731ed055f9a7499530793e96b4557","actor_gravatar":"631762ca4bfe6a00ac0d2d1da00f94c1","push_id":28533611}