The patch titled
     fix "softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks"
has been removed from the -mm tree.  Its filename was
     softlockup-automatically-detect-hung-task_uninterruptible-tasks.patch

This patch was dropped because it is obsolete

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: fix "softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks"
From: Ingo Molnar <[EMAIL PROTECTED]>


Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 arch/x86/kernel/reboot.c |   16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff -puN 
arch/x86/kernel/reboot.c~softlockup-automatically-detect-hung-task_uninterruptible-tasks
 arch/x86/kernel/reboot.c
--- 
a/arch/x86/kernel/reboot.c~softlockup-automatically-detect-hung-task_uninterruptible-tasks
+++ a/arch/x86/kernel/reboot.c
@@ -396,8 +396,20 @@ void machine_shutdown(void)
        if (!cpu_isset(reboot_cpu_id, cpu_online_map))
                reboot_cpu_id = smp_processor_id();
 
-       /* Make certain I only run on the appropriate processor */
-       set_cpus_allowed(current, cpumask_of_cpu(reboot_cpu_id));
+       /*
+        * Make certain we only run on the appropriate processor,
+        * and with sufficient priority:
+        */
+       {
+               struct sched_param schedparm;
+               schedparm.sched_priority = 99;
+               int ret;
+
+               ret = sched_setscheduler(current, SCHED_RR, &schedparm);
+               WARN_ON_ONCE(1);
+
+               set_cpus_allowed(current, cpumask_of_cpu(reboot_cpu_id));
+       }
 
        /* O.K Now that I'm on the appropriate processor,
         * stop all of the others.
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch
documentation-create-new-scheduler-subdirectory.patch
add-cmpxchg64-and-cmpxchg64_local-to-x86_64.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to