qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qapi: add dirty bitmap status
Date: Fri, 22 May 2015 13:27:41 -0400	[thread overview]
Message-ID: <555F670D.5010307@redhat.com> (raw)
In-Reply-To: <87y4kht2oc.fsf@blackfin.pond.sub.org>



On 05/22/2015 04:52 AM, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
> 
>> 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>
> 
> Patch does two things:
> 
> 1. Convert status from bool frozen to enum.
> 2. Add new status 'disabled'.
> 
> I would've done this separately, but it's no big deal.  But I think we
> should spell it out in the commit message.
> 
> What about:
> 
>     qapi: add dirty bitmap status
> 
>     Bitmaps can be in a handful of different states with potentially
>     more to come as we tool around with migration and persistence patches.
> 
>     Management applications may need to know why certain bitmaps are
>     unavailable for various commands, e.g. busy in another operation,
>     busy being migrated, etc.
> 
>     Right now, all we offer is BlockDirtyInfo's boolean member 'frozen'.
>     Instead of adding more booleans, replace it by an enumeration member
>     'status' with values 'active' and 'frozen'.  Then add new value
>     'disabled'.
> 
>     Incompatible change.  Fine because the changed part hasn't been
>     released so far.
> 
>     Suggested-by: Eric Blake <eblake@redhat.com>
>     Signed-off-by: John Snow <jsnow@redhat.com>
>     Reviewed-by: Eric Blake <eblake@redhat.com>
>     [Commit message tweaked]
>     Signed-off-by: Markus Armbruster <armbru@redhat.com>
> 

This is OK by me, Markus. I'll assume that you are OK with or have
already made these changes locally, so I won't resend.

Thank you,
--John

  reply	other threads:[~2015-05-22 17:27 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
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 [this message]
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=555F670D.5010307@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).