[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Oct 2011 12:48:59 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, pavel@....cz,
len.brown@...el.com, mingo@...e.hu, akpm@...ux-foundation.org,
suresh.b.siddha@...el.com, lucas.demarchi@...fusion.mobi,
linux-pm@...ts.linux-foundation.org, rusty@...tcorp.com.au,
vatsa@...ux.vnet.ibm.com, ashok.raj@...el.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] CPU hotplug, freezer: Fix bugs in CPU hotplug call
path
On Sat, 2011-10-08 at 02:26 +0530, Srivatsa S. Bhat wrote:
>
> So, we should mutually exclude cpu hotplugging and freezing/thawing to
> ensure that during the entire duration that the callbacks for the notified
> event are running, the state introduced by that event holds good.
Yes we should, but I'd rather see that done on a more fundamental level,
and not frob yet another mutex in the already complex hotplug system.
--
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