Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754078AbaAWO1q (ORCPT ); Thu, 23 Jan 2014 09:27:46 -0500 Received: from mail-oa0-f46.google.com ([209.85.219.46]:36888 "EHLO mail-oa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752353AbaAWO1p (ORCPT ); Thu, 23 Jan 2014 09:27:45 -0500 MIME-Version: 1.0 In-Reply-To: <20140123135430.GB13345@localhost.localdomain> References: <20140120154058.GA9436@localhost.localdomain> <20140123135430.GB13345@localhost.localdomain> Date: Thu, 23 Jan 2014 19:57:44 +0530 Message-ID: Subject: Re: [QUERY]: Is using CPU hotplug right for isolating CPUs? From: Viresh Kumar To: Frederic Weisbecker Cc: Lei Wen , Kevin Hilman , Lists linaro-kernel , Peter Zijlstra , Linux Kernel Mailing List , Steven Rostedt , Linaro Networking , Tejun Heo Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23 January 2014 19:24, Frederic Weisbecker 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/