qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 01/11] snapshot: create helper to test that block drivers supports snapshots
Date: Thu, 5 Nov 2015 10:58:44 +0300	[thread overview]
Message-ID: <563B0C34.4020004@openvz.org> (raw)
In-Reply-To: <20151105072650.6c35f118@bahia.local>

On 11/05/2015 09:26 AM, Greg Kurz wrote:
> On Wed,  4 Nov 2015 20:19:32 +0300
> "Denis V. Lunev" <den@openvz.org> wrote:
>
>> The patch enforces proper locking for this operation.
>>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Juan Quintela <quintela@redhat.com>
>> CC: Stefan Hajnoczi <stefanha@redhat.com>
>> CC: Kevin Wolf <kwolf@redhat.com>
>> ---
>>   block/snapshot.c         | 27 +++++++++++++++++++++++++++
>>   include/block/snapshot.h |  9 +++++++++
>>   migration/savevm.c       | 17 ++++-------------
>>   3 files changed, 40 insertions(+), 13 deletions(-)
>>
>> diff --git a/block/snapshot.c b/block/snapshot.c
>> index 89500f2..2ef4545 100644
>> --- a/block/snapshot.c
>> +++ b/block/snapshot.c
>> @@ -356,3 +356,30 @@ int bdrv_snapshot_load_tmp_by_id_or_name(BlockDriverState *bs,
>>
>>       return ret;
>>   }
>> +
>> +
>> +/* Group operations. All block drivers are involved.
>> + * These functions will properly handle dataplace (take aio_context_acquire
> s/dataplace/dataplane
>
>> + * when appropriate for appropriate block drivers
> Missing ) and anyway the "(take aio_context_acquire..." part more or less
> quotes the code and is not needed.
>
>> + *
>> + * Returned block driver will be always locked.
>> + */
>> +
>> +bool bdrv_all_can_snapshot(BlockDriverState **first_bad_bs)
> Juan suggested bdrv_snapshot_is_possible() and FWIW you already emphasize
> that it involves all block drivers in the above comment.
>
>> +{
>> +    bool ok = true;
>> +    BlockDriverState *bs = NULL;
>> +
>> +    while ((bs = bdrv_next(bs)) && ok) {
>> +        AioContext *ctx = bdrv_get_aio_context(bs);
>> +
>> +        aio_context_acquire(ctx);
>> +        if (bdrv_is_inserted(bs) && !bdrv_is_read_only(bs)) {
>> +            ok = bdrv_can_snapshot(bs);
>> +        }
>> +        aio_context_release(ctx);
>> +    }
>> +
>> +    *first_bad_bs = bs;
>> +    return ok;
>> +}
>> diff --git a/include/block/snapshot.h b/include/block/snapshot.h
>> index 770d9bb..0a3cf0d 100644
>> --- a/include/block/snapshot.h
>> +++ b/include/block/snapshot.h
>> @@ -75,4 +75,13 @@ int bdrv_snapshot_load_tmp(BlockDriverState *bs,
>>   int bdrv_snapshot_load_tmp_by_id_or_name(BlockDriverState *bs,
>>                                            const char *id_or_name,
>>                                            Error **errp);
>> +
>> +
>> +/* Group operations. All block drivers are involved.
>> + * These functions will properly handle dataplace (take aio_context_acquire
>> + * when appropriate for appropriate block drivers
>> + *
>> + */
> This comment is not needed here, already in block/snapshot.c
it is better to have it twice.


>> +bool bdrv_all_can_snapshot(BlockDriverState **first_bad_bs);
>> +
>>   #endif
>> diff --git a/migration/savevm.c b/migration/savevm.c
>> index dbcc39a..3ac3f07 100644
>> --- a/migration/savevm.c
>> +++ b/migration/savevm.c
>> @@ -1290,19 +1290,10 @@ void hmp_savevm(Monitor *mon, const QDict *qdict)
>>       const char *name = qdict_get_try_str(qdict, "name");
>>       Error *local_err = NULL;
>>
>> -    /* Verify if there is a device that doesn't support snapshots and is writable */
>> -    bs = NULL;
>> -    while ((bs = bdrv_next(bs))) {
>> -
>> -        if (!bdrv_is_inserted(bs) || bdrv_is_read_only(bs)) {
>> -            continue;
>> -        }
>> -
>> -        if (!bdrv_can_snapshot(bs)) {
>> -            monitor_printf(mon, "Device '%s' is writable but does not support snapshots.\n",
>> -                               bdrv_get_device_name(bs));
>> -            return;
>> -        }
>> +    if (!bdrv_all_can_snapshot(&bs)) {
>> +        monitor_printf(mon, "Device '%s' is writable but does not "
>> +                       "support snapshots.\n", bdrv_get_device_name(bs));
>> +        return;
>>       }
>>
>>       bs = find_vmstate_bs();
> Reviewed-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
>
Thank you for spelling check.

  reply	other threads:[~2015-11-05  7:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 17:19 [Qemu-devel] [PATCH 2.5 v5 0/11] dataplane snapshot fixes Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 01/11] snapshot: create helper to test that block drivers supports snapshots Denis V. Lunev
2015-11-05  6:26   ` Greg Kurz
2015-11-05  7:58     ` Denis V. Lunev [this message]
2015-11-06 13:53     ` Stefan Hajnoczi
2015-11-04 17:19 ` [Qemu-devel] [PATCH 02/11] snapshot: return error code from bdrv_snapshot_delete_by_id_or_name Denis V. Lunev
2015-11-05  7:55   ` Greg Kurz
2015-11-05  8:02     ` Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 03/11] snapshot: create bdrv_all_delete_snapshot helper Denis V. Lunev
2015-11-06 14:09   ` Stefan Hajnoczi
2015-11-06 14:12     ` Denis V. Lunev
2015-11-07 12:22     ` Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 04/11] snapshot: create bdrv_all_goto_snapshot helper Denis V. Lunev
2015-11-05  9:09   ` Greg Kurz
2015-11-04 17:19 ` [Qemu-devel] [PATCH 05/11] snapshot: create bdrv_all_find_snapshot helper Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 06/11] migration: drop find_vmstate_bs check in hmp_delvm Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 07/11] migration: reorder processing in hmp_savevm Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 08/11] migration: implement bdrv_all_find_vmstate_bs and bdrv_unlock helpers Denis V. Lunev
2015-11-06 15:18   ` Stefan Hajnoczi
2015-11-06 15:23     ` Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 09/11] migration: add missed aio_context_acquire for state writing/reading Denis V. Lunev
2015-11-06 15:37   ` Stefan Hajnoczi
2015-11-04 17:19 ` [Qemu-devel] [PATCH 10/11] snapshot: create bdrv_all_create_snapshot helper Denis V. Lunev
2015-11-04 17:19 ` [Qemu-devel] [PATCH 11/11] monitor: add missed aio_context_acquire into vm_completion call Denis V. Lunev
2015-11-06 15:40   ` Stefan Hajnoczi
2015-11-06 15:54 ` [Qemu-devel] [PATCH 2.5 v5 0/11] dataplane snapshot fixes Stefan Hajnoczi
2015-11-06 16:05   ` Eric Blake
2015-11-06 16:19     ` Denis V. Lunev
2015-11-06 17:29       ` Stefan Hajnoczi
2015-11-06 21:13     ` Denis V. Lunev
2015-11-09 21:05       ` Eric Blake
2015-11-10 12:55         ` Denis V. Lunev
  -- strict thread matches above, loose matches on Subject: below --
2015-11-17  9:08 [Qemu-devel] [PATCH for 2.9 v8 0/10] " Denis V. Lunev
2015-11-17  9:08 ` [Qemu-devel] [PATCH 01/11] snapshot: create helper to test that block drivers supports snapshots Denis V. Lunev
2015-11-18 10:57   ` Juan Quintela
2015-11-19  6:42 [Qemu-devel] [PATCH for 2.5 v10 0/10] dataplane snapshot fixes Denis V. Lunev
2015-11-19  6:42 ` [Qemu-devel] [PATCH 01/11] snapshot: create helper to test that block drivers supports snapshots Denis V. Lunev

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=563B0C34.4020004@openvz.org \
    --to=den@openvz.org \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@redhat.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).