summaryrefslogtreecommitdiff
path: root/tools/perf/arch/s390/util/kvm-stat.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 14:25:17 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 14:25:17 -0800
commit566cf877a1fcb6d6dc0126b076aad062054c2637 (patch)
treec6d5b5de629b0adfaced9d629ed06777c6b6a26c /tools/perf/arch/s390/util/kvm-stat.c
parent39cb2c9a316e77f6dfba96c543e55b6672d5a37e (diff)
Linux 4.10-rc6
Diffstat (limited to 'tools/perf/arch/s390/util/kvm-stat.c')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-27 17:13:43 +0000
->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'tools/perf/Documentation/perf-kmem.txt')