On Wed, Oct 03, 2012 at 08:29:54AM +0530, Preeti U Murthy wrote: > From: Srivatsa S. Bhat <[email protected]> > > In the event of CPU hotplug, the kernel modifies the cpusets' > cpus_allowed masks as and when necessary to ensure that the tasks belonging > to the > cpusets have some place (online CPUs) to run on. And regular CPU hotplug is > destructive in the sense that the kernel doesn't remember the original cpuset > configurations set by the user, across hotplug operations. > > However, suspend/resume (which uses CPU hotplug) is a special case in > which the kernel has the responsibility to restore the system (during > resume), to exactly the same state it was in before suspend. > > commit d35be8bab9b0ce44bed4b9453f86ebf64062721e > Author: Srivatsa S. Bhat <[email protected]> > Date: Thu May 24 19:46:26 2012 +0530 > > CPU hotplug, cpusets, suspend: Don't modify cpusets during > suspend/resume > > Please apply this patch to the stable trees 3.5.y, 3.4.y
Ah, ok, that makes more sense, I shouldn't have responded so quickly. But, you copied a non-public mailing list, and you should still notify the people who originally signed off on this patch to ensure they don't object to it. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
