[Top][All Lists]

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

Re: [Qemu-devel] [PATCH for-2.12 0/4] qmp dirty bitmap API

From: John Snow
Subject: Re: [Qemu-devel] [PATCH for-2.12 0/4] qmp dirty bitmap API
Date: Wed, 15 Nov 2017 16:20:59 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 11/13/2017 11:20 AM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
> There are three qmp commands, needed to implement external backup API.
> Using these three commands, client may do all needed bitmap management by
> hand:
> on backup start we need to do a transaction:
>  {disable old bitmap, create new bitmap}
> on backup success:
>  drop old bitmap
> on backup fail:
>  enable old bitmap
>  merge new bitmap to old bitmap
>  drop new bitmap

Can you give me an example of how you expect these commands to be used,
and why they're required?

I'm a little weary about how error-prone these commands might be and the
potential for incorrect usage seems... high. Why do we require them?

reply via email to

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