[patch] don't change cpus_allowed for task initiating the suspend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Don't modify the cpus_allowed of the task initiating the suspend. 
_cpu_down() already makes sure that the task doing the suspend doesn't
run on dying cpu.

Signed-off-by: Suresh Siddha <[email protected]>
Cc: Venkatesh Pallipadi <[email protected]>
---

diff --git a/kernel/cpu.c b/kernel/cpu.c
index 663c920..d21756a 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -270,11 +270,7 @@ int disable_nonboot_cpus(void)
 			goto out;
 		}
 	}
-	error = set_cpus_allowed(current, cpumask_of_cpu(first_cpu));
-	if (error) {
-		printk(KERN_ERR "Could not run on CPU%d\n", first_cpu);
-		goto out;
-	}
+
 	/* We take down all of the non-boot CPUs in one shot to avoid races
 	 * with the userspace trying to use the CPU hotplug at the same time
 	 */
-
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/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux