qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 09/11] migration: add missed aio_context_acquire


From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] [PATCH 09/11] migration: add missed aio_context_acquire for state writing/reading
Date: Fri, 6 Nov 2015 15:37:04 +0000
User-agent: Mutt/1.5.23 (2015-06-09)

On Wed, Nov 04, 2015 at 08:19:40PM +0300, Denis V. Lunev wrote:
> aio_context should be locked in the similar way as was done in QMP
> snapshot creation in the other case there are a lot of possible
> troubles if native AIO mode is enabled for disk.
> 
> qemu_fopen_bdrv and bdrv_fclose are used in real snapshot operations only
> along with block drivers. This change should influence only HMP snapshot
> operations.
> 
> AioContext lock is reqursive. Thus nested locking should not be a problem.

hmp_savevm() and load_vmstate() look up the BlockDriverState and perform
other operations on it.  So the natural place to call acquire/release is
in hmp_savevm() and load_vmstate().  They need that anyway since they
also perform other operations.

qemu_fopen_bdrv() and bdrv_fclose() don't need to worry about
AioContext.

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]