| commit | e5c67ab552fb056827b5b40356c0ef235e975e7e | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Mon, 13 Feb 2017 13:52:26 +0000 (13 14:52 +0100) | ||
| committer | Stefan Hajnoczi <stefanha@redhat.com> | |
| Tue, 21 Feb 2017 11:14:08 +0000 (21 11:14 +0000) | ||
| tree | 2e92976f6ed2d2c58cd6a0faee223fcdca08cc77 | treesnapshot (tar.gz zip) |
| parent | a9d9235567e7637d474fa9a52432c63c9feeed07 | commitdiff |
blkdebug: reschedule coroutine on the AioContext it is running on
Keep the coroutine on the same AioContext. Without this change,
there would be a race between yielding the coroutine and reentering it.
While the race cannot happen now, because the code only runs from a single
AioContext, this will change with multiqueue support in the block layer.
While doing the change, replace custom bottom half with aio_co_schedule.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170213135235.12274-10-pbonzini@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Keep the coroutine on the same AioContext. Without this change,
there would be a race between yielding the coroutine and reentering it.
While the race cannot happen now, because the code only runs from a single
AioContext, this will change with multiqueue support in the block layer.
While doing the change, replace custom bottom half with aio_co_schedule.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 20170213135235.12274-10-pbonzini@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
| block/blkdebug.c | diffblobblamehistory |