| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 May 2012 14:24:15 -0700 (PDT) From: David Rientjes <rientjes@...gle.com> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> cc: Nishanth Aravamudan <nacc@...ux.vnet.ibm.com>, "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>, mingo@...nel.org, pjt@...gle.com, paul@...lmenage.org, akpm@...ux-foundation.org, rjw@...k.pl, nacc@...ibm.com, paulmck@...ux.vnet.ibm.com, tglx@...utronix.de, seto.hidetoshi@...fujitsu.com, tj@...nel.org, mschmidt@...hat.com, berrange@...hat.com, nikunj@...ux.vnet.ibm.com, vatsa@...ux.vnet.ibm.com, liuj97@...il.com, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org Subject: Re: [PATCH v3 5/5] cpusets, suspend: Save and restore cpusets during suspend/resume On Tue, 15 May 2012, Peter Zijlstra wrote: > > Why can't we leave cpuset.cpus unaltered for all cpusets during suspend? > > We can, that's what Srivatsa is going to make. The only thing I object > to is the !suspend hotplug case. > Srivatsa is going to do that in another patchset in addition to this one? We shouldn't need to store any old cpumask at all, just allow cpuset.cpus to be a superset of online cpus during s/r and don't touch cpusets at all since the cpus, as you said, are guaranteed to come back. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists