[libvirt] [PATCH v3 06/10] block/dirty-bitmap: explicitly lock bitmaps with successors
Vladimir Sementsov-Ogievskiy
vsementsov at virtuozzo.com
Mon Feb 25 07:48:55 UTC 2019
23.02.2019 3:06, John Snow wrote:
> Instead of implying a user_locked/busy status, make it explicit.
> Now, bitmaps in use by migration, NBD or backup operations
> are all treated the same way with the same code paths.
>
> Signed-off-by: John Snow<jsnow at redhat.com>
> Reviewed-by: Eric Blake<eblake at redhat.com>
hmm, you forget my r-b:
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov at virtuozzo.com>
--
Best regards,
Vladimir
More information about the libvir-list
mailing list