diff options
| author | Fiona Ebner <f.ebner@proxmox.com> | 2025-05-30 17:11:00 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2025-07-14 15:40:45 +0200 |
| commit | 502f00c51ad9a133c728b52e96c7e8e0cffef191 (patch) | |
| tree | b2d872060d92bdb2710ff661701cd7cfe2953735 /scripts/tracetool/backend | |
| parent | 9a4e273ddec3927920c5958d2226c6b38b543336 (diff) | |
| download | qemu-502f00c51ad9a133c728b52e96c7e8e0cffef191.zip qemu-502f00c51ad9a133c728b52e96c7e8e0cffef191.tar.gz qemu-502f00c51ad9a133c728b52e96c7e8e0cffef191.tar.bz2 | |
block: never use atomics to access bs->quiesce_counter
All accesses of bs->quiesce_counter are in the main thread, either
after a GLOBAL_STATE_CODE() macro or in a function with GRAPH_WRLOCK
annotation.
This is essentially a revert of 414c2ec358 ("block: access
quiesce_counter with atomic ops"). At that time, neither the
GLOBAL_STATE_CODE() macro nor the GRAPH_WRLOCK annotation existed.
Even if the field was only accessed in the main thread back then (did
not check if that is actually the case), it wouldn't have been easy to
verify.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Message-ID: <20250530151125.955508-24-f.ebner@proxmox.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'scripts/tracetool/backend')
0 files changed, 0 insertions, 0 deletions