Benjamin Herrenschmidt wrote:
The intention of the cpu_hotplug_driver_locks to add additional serialization
during cpu hotplug operations. For pseries this is used during DLPAR of cpu
operations so that cpu hotplug actions cannot be initiated whiloe a DLPAR
operation is in flight. For example,
The intention of the cpu_hotplug_driver_locks to add additional serialization
during cpu hotplug operations. For pseries this is used during DLPAR of cpu
operations so that cpu hotplug actions cannot be initiated whiloe a DLPAR
operation is in flight. For example, during DLPAR add we take
Michael Ellerman wrote:
On Tue, 2009-12-22 at 08:45 -0600, Nathan Fontenot wrote:
The recently introduced cpu_hotplug_driver_lock used to serialize
cpu hotplug operations, namely for the pseries platform, causes a build
issue for other platforms. The base cpu hotplug code attempts
to take this
On Wed, 2009-12-23 at 08:48 -0600, Nathan Fontenot wrote:
Michael Ellerman wrote:
On Tue, 2009-12-22 at 08:45 -0600, Nathan Fontenot wrote:
The recently introduced cpu_hotplug_driver_lock used to serialize
cpu hotplug operations, namely for the pseries platform, causes a build
issue for
The recently introduced cpu_hotplug_driver_lock used to serialize
cpu hotplug operations, namely for the pseries platform, causes a build
issue for other platforms. The base cpu hotplug code attempts
to take this lock, but it may not be needed for all platforms. This patch
moves the lock/unlock
On Tue, 2009-12-22 at 08:45 -0600, Nathan Fontenot wrote:
The recently introduced cpu_hotplug_driver_lock used to serialize
cpu hotplug operations, namely for the pseries platform, causes a build
issue for other platforms. The base cpu hotplug code attempts
to take this lock, but it may not
