mirror of
https://gitlab.com/qemu-project/qemu
synced 2024-09-06 09:55:55 +00:00
![]() When invoked from the main loop, this function is the same as qemu_mutex_iothread_locked, and returns true if the BQL is held. When invoked from iothreads or tests, it returns true only if the current AioContext is the Main Loop. This essentially just extends qemu_mutex_iothread_locked to work also in unit tests or other users like storage-daemon, that run in the Main Loop but end up using the implementation in stubs/iothread-lock.c. Using qemu_mutex_iothread_locked in unit tests defaults to false because they use the implementation in stubs/iothread-lock, making all assertions added in next patches fail despite the AioContext is still the main loop. See the comment in the function header for more information. Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com> Message-Id: <20220303151616.325444-2-eesposit@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> |
||
---|---|---|
.. | ||
bdrv-next-monitor-owned.c | ||
blk-commit-all.c | ||
blk-exp-close-all.c | ||
blockdev-close-all-bdrv-states.c | ||
change-state-handler.c | ||
cmos.c | ||
cpu-get-clock.c | ||
cpu-synchronize-state.c | ||
cpus-get-virtual-clock.c | ||
dump.c | ||
error-printf.c | ||
fdset.c | ||
fw_cfg.c | ||
gdbstub.c | ||
get-vm-name.c | ||
icount.c | ||
io_uring.c | ||
iothread-lock-block.c | ||
iothread-lock.c | ||
is-daemonized.c | ||
isa-bus.c | ||
linux-aio.c | ||
meson.build | ||
migr-blocker.c | ||
module-opts.c | ||
monitor-core.c | ||
monitor.c | ||
pci-bus.c | ||
qdev.c | ||
qemu-timer-notify-cb.c | ||
qmp-command-available.c | ||
qmp-quit.c | ||
qmp_memory_device.c | ||
qtest.c | ||
ram-block.c | ||
ramfb.c | ||
replay-tools.c | ||
replay.c | ||
runstate-check.c | ||
semihost.c | ||
sysbus.c | ||
target-get-monitor-def.c | ||
target-monitor-defs.c | ||
trace-control.c | ||
usb-dev-stub.c | ||
uuid.c | ||
vm-stop.c | ||
vmgenid.c | ||
vmstate.c | ||
win32-kbd-hook.c | ||
xen-hw-stub.c |