From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
pavel@ucw.cz, len.brown@intel.com, mingo@elte.hu,
akpm@linux-foundation.org, suresh.b.siddha@intel.com,
lucas.demarchi@profusion.mobi,
"linux-pm@vger.kernel.org >> Linux PM mailing list"
<linux-pm@vger.kernel.org>,
rusty@rustcorp.com.au, vatsa@linux.vnet.ibm.com,
ashok.raj@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] CPU hotplug, freezer: Fix bugs in CPU hotplug call path
Date: Fri, 21 Oct 2011 17:00:17 +0530 [thread overview]
Message-ID: <4EA157C9.30500@linux.vnet.ibm.com> (raw)
In-Reply-To: <1318243739.14400.10.camel@laptop>
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@linux.vnet.ibm.com>
Linux Technology Center,
IBM India Systems and Technology Lab
prev parent reply other threads:[~2011-10-21 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 19:44 [PATCH] CPU hotplug, freezer: Fix bugs in CPU hotplug call path Srivatsa S. Bhat
2011-10-03 10:03 ` Peter Zijlstra
2011-10-04 13:19 ` Srivatsa S. Bhat
2011-10-04 13:28 ` [PATCH v2] " Srivatsa S. Bhat
2011-10-04 13:37 ` Peter Zijlstra
2011-10-07 20:56 ` Srivatsa S. Bhat
2011-10-08 12:52 ` Américo Wang
2011-10-08 20:28 ` Srivatsa S. Bhat
2011-10-10 10:48 ` Peter Zijlstra
2011-10-21 11:30 ` Srivatsa S. Bhat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA157C9.30500@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=ashok.raj@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=vatsa@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).