From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:40933) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gtMTk-0003Tm-Kk for qemu-devel@nongnu.org; Mon, 11 Feb 2019 20:03:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gtMTi-0007vK-7x for qemu-devel@nongnu.org; Mon, 11 Feb 2019 20:03:16 -0500 From: John Snow Date: Mon, 11 Feb 2019 20:02:43 -0500 Message-Id: <20190212010248.11056-1-jsnow@redhat.com> Subject: [Qemu-devel] [PATCH 0/5] dirty-bitmaps: deprecate @status field List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: John Snow , Kevin Wolf , Stefan Hajnoczi , Juan Quintela , qemu-block@nongnu.org, Fam Zheng , eblake@redhat.com, vsementsov@virtuozzo.com, "Dr. David Alan Gilbert" , Max Reitz , Markus Armbruster The current internal meanings of "locked", "user_locked", "qmp_locked", "frozen", "enabled", and "disabled" are all a little muddled. Deprecate the @status field in favor of two new booleans that carry very specific meanings. Then, rename and rework some of the internal semantics to help make the API a bit more clear and easier to read. Well, in my opinion. Based on my current bitmaps branch (includes Eric's patch and my documentation update patch.) John Snow (5): block/dirty-bitmap: add recording and busy properties block/dirty-bitmaps: rename frozen predicate helper block/dirty-bitmap: change semantics of enabled predicate block/dirty-bitmap: explicitly lock bitmaps with successors block/dirty-bitmaps: unify qmp_locked and user_locked calls block/dirty-bitmap.c | 74 +++++++++++++++++++--------------- blockdev.c | 18 ++++----- include/block/dirty-bitmap.h | 7 ++-- migration/block-dirty-bitmap.c | 8 ++-- nbd/server.c | 6 +-- qapi/block-core.json | 9 ++++- tests/qemu-iotests/236.out | 28 +++++++++++++ 7 files changed, 96 insertions(+), 54 deletions(-) -- 2.17.2