diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2023-12-05 13:20:11 -0500 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2023-12-21 22:49:27 +0100 |
| commit | 23c983c8f6b2fea22698f501aa6a2c03dadd81ba (patch) | |
| tree | 405001c138d88aa6aee3001243e467ba26a8b7bb /qapi/string-output-visitor.c | |
| parent | e91083cd3f082c4d26a7d52268cbd57fc81def28 (diff) | |
| download | focaccia-qemu-23c983c8f6b2fea22698f501aa6a2c03dadd81ba.tar.gz focaccia-qemu-23c983c8f6b2fea22698f501aa6a2c03dadd81ba.zip | |
block: remove outdated AioContext locking comments
The AioContext lock no longer exists. There is one noteworthy change: - * More specifically, these functions use BDRV_POLL_WHILE(bs), which - * requires the caller to be either in the main thread and hold - * the BlockdriverState (bs) AioContext lock, or directly in the - * home thread that runs the bs AioContext. Calling them from - * another thread in another AioContext would cause deadlocks. + * More specifically, these functions use BDRV_POLL_WHILE(bs), which requires + * the caller to be either in the main thread or directly in the home thread + * that runs the bs AioContext. Calling them from another thread in another + * AioContext would cause deadlocks. I am not sure whether deadlocks are still possible. Maybe they have just moved to the fine-grained locks that have replaced the AioContext. Since I am not sure if the deadlocks are gone, I have kept the substance unchanged and just removed mention of the AioContext. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Message-ID: <20231205182011.1976568-15-stefanha@redhat.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'qapi/string-output-visitor.c')
0 files changed, 0 insertions, 0 deletions