[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4EA157C9.30500@linux.vnet.ibm.com>
Date: Fri, 21 Oct 2011 17:00:17 +0530
From: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
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@...r.kernel.org >> Linux PM mailing list"
<linux-pm@...r.kernel.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 10/10/2011 04:18 PM, Peter Zijlstra wrote:
> 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.
>
Sure, thank you for the feedback. I have now come up with another version
that doesn't introduce any new mutex. I'll post it out in a while.
--
Regards,
Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab
--
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