23 Jan
2014
23 Jan
'14
2:27 p.m.
On 23 January 2014 19:24, Frederic Weisbecker fweisbec@gmail.com wrote:
On Tue, Jan 21, 2014 at 10:07:58AM +0800, Lei Wen wrote:
I find the cpuset's cpus member becomes NULL even I hotplug the core3 back again. So is it a bug?
Not sure, you may need to check cpuset internals.
I think this is the correct behavior. Userspace must decide what to do with that CPU once it is back. Simply reverting to earlier cpusets configuration might not be the right approach.
Also, what if cpusets have been rewritten in-between hotplug events.