summaryrefslogtreecommitdiffstats
path: root/drivers/watchdog
diff options
context:
space:
mode:
authorGautham R Shenoy <ego@in.ibm.com>2009-11-26 09:59:05 +0000
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2009-12-09 17:09:36 +1100
commit51badebdcf394cc5fd574a524b55b3f6085e5e9c (patch)
tree2e8173c3995f45a88826d5f453545a2c8dd86621 /drivers/watchdog
parentb6db63d1a7f0138f348ba7a648df35ac6365988e (diff)
downloadblackbird-obmc-linux-51badebdcf394cc5fd574a524b55b3f6085e5e9c.tar.gz
blackbird-obmc-linux-51badebdcf394cc5fd574a524b55b3f6085e5e9c.zip
powerpc/pseries: Serialize cpu hotplug operations during deactivate Vs deallocate
Currently the cpu-allocation/deallocation process comprises of two steps: - Set the indicators and to update the device tree with DLPAR node information. - Online/offline the allocated/deallocated CPU. This is achieved by writing to the sysfs tunables "probe" during allocation and "release" during deallocation. At the sametime, the userspace can independently online/offline the CPUs of the system using the sysfs tunable "online". It is quite possible that when a userspace tool offlines a CPU for the purpose of deallocation and is in the process of updating the device tree, some other userspace tool could bring the CPU back online by writing to the "online" sysfs tunable thereby causing the deallocate process to fail. The solution to this is to serialize writes to the "probe/release" sysfs tunable with the writes to the "online" sysfs tunable. This patch employs a mutex to provide this serialization, which is a no-op on all architectures except PPC_PSERIES Signed-off-by: Gautham R Shenoy <ego@in.ibm.com> Acked-by: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'drivers/watchdog')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud