From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qapi: add dirty bitmap status
Date: Tue, 19 May 2015 17:18:28 -0400 [thread overview]
Message-ID: <555BA8A4.8070407@redhat.com> (raw)
In-Reply-To: <55525D43.6060402@redhat.com>
On 05/12/2015 04:06 PM, Eric Blake wrote:
> On 05/12/2015 01:53 PM, John Snow wrote:
>> Bitmaps can be in a handful of different states with potentially
>> more to come as we tool around with migration and persistence patches.
>>
>> Instead of having a bunch of boolean fields, it was suggested that we
>> just have an enum status field that will help expose the reason to
>> management APIs why certain bitmaps may be unavailable for various
>> commands
>>
>> (e.g. busy in another operation, busy being migrated, etc.)
>
> Might be worth mentioning that this is an API change, but safe because
> the old API is unreleased (and therefore, this patch MUST go in the 2.4
> time frame, if at all).
>
>>
>> Suggested-by: Eric Blake <eblake@redhat.com>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>> block.c | 13 ++++++++++++-
>> include/block/block.h | 1 +
>> qapi/block-core.json | 23 +++++++++++++++++++++--
>> 3 files changed, 34 insertions(+), 3 deletions(-)
>>
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
I'm not actually sure whose tree this should go in. Markus's, perhaps?
("ping")
next prev parent reply other threads:[~2015-05-19 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 19:53 [Qemu-devel] [PATCH] qapi: add dirty bitmap status John Snow
2015-05-12 20:06 ` Eric Blake
2015-05-12 20:07 ` John Snow
2015-05-19 21:18 ` John Snow [this message]
2015-05-20 8:20 ` Markus Armbruster
2015-05-21 21:48 ` John Snow
2015-05-22 8:22 ` Kevin Wolf
2015-05-22 8:31 ` Markus Armbruster
2015-05-22 11:49 ` Kevin Wolf
2015-05-22 17:26 ` John Snow
2015-05-22 15:36 ` John Snow
2015-05-22 8:52 ` Markus Armbruster
2015-05-22 17:27 ` John Snow
2015-05-26 8:13 ` Markus Armbruster
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=555BA8A4.8070407@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).