[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 01/10] block/dirty-bitmap: add recording and
From: |
Vladimir Sementsov-Ogievskiy |
Subject: |
Re: [Qemu-devel] [PATCH v3 01/10] block/dirty-bitmap: add recording and busy properties |
Date: |
Mon, 25 Feb 2019 06:23:08 +0000 |
23.02.2019 3:06, John Snow wrote:
> The current API allows us to report a single status, which we've defined as:
>
> Frozen: has a successor, treated as qmp_locked, may or may not be enabled.
> Locked: no successor, qmp_locked. may or may not be enabled.
> Disabled: Not frozen or locked, disabled.
> Active: Not frozen, locked, or disabled.
>
> The problem is that both "Frozen" and "Locked" mean nearly the same thing,
> and that both of them do not intuit whether they are recording guest writes
> or not.
>
> This patch deprecates that status field and introduces two orthogonal
> properties instead to replace it.
>
> Signed-off-by: John Snow<address@hidden>
Reviewed-by: Vladimir Sementsov-Ogievskiy <address@hidden>
--
Best regards,
Vladimir
- [Qemu-devel] [PATCH v3 00/10] dirty-bitmaps: deprecate @status field, John Snow, 2019/02/22
- [Qemu-devel] [PATCH v3 02/10] block/dirty-bitmaps: rename frozen predicate helper, John Snow, 2019/02/22
- [Qemu-devel] [PATCH v3 01/10] block/dirty-bitmap: add recording and busy properties, John Snow, 2019/02/22
- [Qemu-devel] [PATCH v3 04/10] block/dirty-bitmap: change semantics of enabled predicate, John Snow, 2019/02/22
- [Qemu-devel] [PATCH v3 09/10] blockdev: remove unused paio parameter documentation, John Snow, 2019/02/22
- [Qemu-devel] [PATCH v3 06/10] block/dirty-bitmap: explicitly lock bitmaps with successors, John Snow, 2019/02/22