Convert qemu_bh_schedule() to qemu_bh_schedule_event(), which can specify the clock type, making it compatible with record-replay.
aio_wait_kick does not affect target machine state, so it should use QEMU_CLOCK_REALTIME so it is not recorded and replayed. Signed-off-by: Nicholas Piggin <npig...@gmail.com> --- util/aio-wait.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/util/aio-wait.c b/util/aio-wait.c index b5336cf5fd2..2137abd4d29 100644 --- a/util/aio-wait.c +++ b/util/aio-wait.c @@ -51,7 +51,8 @@ void aio_wait_kick(void) smp_mb(); if (qatomic_read(&global_aio_wait.num_waiters)) { - aio_bh_schedule_oneshot(qemu_get_aio_context(), dummy_bh_cb, NULL); + aio_bh_schedule_oneshot_event(qemu_get_aio_context(), dummy_bh_cb, + NULL, QEMU_CLOCK_REALTIME); } } -- 2.45.2