[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpo=VoXbGmCXokK_MDC=oq7WievXH7-=JtMVWOQaYu3iaMw@mail.gmail.com>
Date: Thu, 23 Jan 2014 19:57:44 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Lei Wen <adrian.wenl@...il.com>, Kevin Hilman <khilman@...aro.org>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Linaro Networking <linaro-networking@...aro.org>,
Tejun Heo <tj@...nel.org>
Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs?
On 23 January 2014 19:24, Frederic Weisbecker <fweisbec@...il.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.
--
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