From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] block/dirty-bitmap: implement inconsistent bit
Date: Wed, 20 Feb 2019 07:46:35 -0600 [thread overview]
Message-ID: <99d8fb0e-d5de-126c-62d4-248153b42726@redhat.com> (raw)
In-Reply-To: <c2188cb6-31fe-28e2-647d-42ae2f12212a@redhat.com>
On 2/19/19 4:00 PM, John Snow wrote:
>>
>> hmm, I also think we should report our deprecated status as locked for inconsistent bitmaps..
>>
>>
>
> Though we're trying to deprecate the field altogether, I *could* add a
> special status flag that makes it unambiguous. This will catch the
> attention of anyone using the old API.
Adding to the enum, even though it is going away in the future, is still
helpful in the present, so I can live with that approach.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-02-20 16:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 23:36 [Qemu-devel] [RFC PATCH 0/2] bitmaps: add inconsistent bit John Snow
2019-02-13 23:36 ` [Qemu-devel] [RFC PATCH 1/2] block/dirty-bitmaps: " John Snow
2019-02-18 17:46 ` Vladimir Sementsov-Ogievskiy
2019-02-19 0:46 ` John Snow
2019-02-13 23:36 ` [Qemu-devel] [RFC PATCH 2/2] block/dirty-bitmap: implement " John Snow
2019-02-18 18:13 ` Vladimir Sementsov-Ogievskiy
2019-02-18 20:37 ` Eric Blake
2019-02-18 23:48 ` John Snow
2019-02-19 22:00 ` John Snow
2019-02-20 9:05 ` Vladimir Sementsov-Ogievskiy
2019-02-20 13:46 ` Eric Blake [this message]
2019-02-18 18:10 ` [Qemu-devel] [RFC PATCH 0/2] bitmaps: add " Vladimir Sementsov-Ogievskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99d8fb0e-d5de-126c-62d4-248153b42726@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).