[Qemu-block] [PATCH 1/5] block/dirty-bitmap: add recording and busy properties

2019-02-11 Thread John Snow
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. T

Re: [Qemu-block] [PATCH 1/5] block/dirty-bitmap: add recording and busy properties

2019-02-12 Thread Eric Blake
On 2/11/19 7:02 PM, 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, disabl

Re: [Qemu-block] [PATCH 1/5] block/dirty-bitmap: add recording and busy properties

2019-02-12 Thread John Snow
On 2/12/19 1:17 PM, Eric Blake wrote: > On 2/11/19 7:02 PM, 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 ena

Re: [Qemu-block] [PATCH 1/5] block/dirty-bitmap: add recording and busy properties

2019-02-13 Thread Vladimir Sementsov-Ogievskiy
On 12.02.2019 1:02, 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, dis