summaryrefslogtreecommitdiffstats
path: root/firmware/whiteheat_loader.HEX
diff options
context:
space:
mode:
authorLai Jiangshan <laijs@cn.fujitsu.com>2013-02-19 12:17:02 -0800
committerTejun Heo <tj@kernel.org>2013-03-04 09:44:58 -0800
commitb31041042a8cdece67f925e4bae55b5f5fd754ca (patch)
tree6392271c537c05d59e0d72ac72463343d2a29249 /firmware/whiteheat_loader.HEX
parentf36dc67b27a689eeb3631b11ebef17bbff257fbb (diff)
downloadop-kernel-dev-b31041042a8cdece67f925e4bae55b5f5fd754ca.zip
op-kernel-dev-b31041042a8cdece67f925e4bae55b5f5fd754ca.tar.gz
workqueue: better define synchronization rule around rescuer->pool updates
Rescuers visit different worker_pools to process work items from pools under pressure. Currently, rescuer->pool is updated outside any locking and when an outsider looks at a rescuer, there's no way to tell when and whether rescuer->pool is gonna change. While this doesn't currently cause any problem, it is nasty. With recent worker_maybe_bind_and_lock() changes, we can move rescuer->pool updates inside pool locks such that if rescuer->pool equals a locked pool, it's guaranteed to stay that way until the pool is unlocked. Move rescuer->pool inside pool->lock. This patch doesn't introduce any visible behavior difference. tj: Updated the description. Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'firmware/whiteheat_loader.HEX')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud