qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: aliguori@us.ibm.com, sheepdog@lists.wpkg.org,
	kvm@vger.kernel.org, qemu-devel@nongnu.org,
	fujita.tomonori@lab.ntt.co.jp, avi@redhat.com, hch@lst.de
Subject: Re: [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers
Date: Mon, 17 May 2010 13:08:08 +0200	[thread overview]
Message-ID: <4BF12398.2040203@redhat.com> (raw)
In-Reply-To: <1274091589-19991-3-git-send-email-morita.kazutaka@lab.ntt.co.jp>

Am 17.05.2010 12:19, schrieb MORITA Kazutaka:
> When snapshot handlers are not defined in the format driver, it is
> better to call the ones of the protocol driver.  This enables us to
> implement snapshot support in the protocol driver.
> 
> We need to call bdrv_close() and bdrv_open() handlers of the format
> driver before and after bdrv_snapshot_goto() call of the protocol.  It is
> because the contents of the block driver state may need to be changed
> after loading vmstate.
> 
> Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
> ---
>  block.c |   61 +++++++++++++++++++++++++++++++++++++++++++------------------
>  1 files changed, 43 insertions(+), 18 deletions(-)
> 
> diff --git a/block.c b/block.c
> index f3bf3f2..c987e57 100644
> --- a/block.c
> +++ b/block.c
> @@ -1683,9 +1683,11 @@ int bdrv_save_vmstate(BlockDriverState *bs, const uint8_t *buf,
>      BlockDriver *drv = bs->drv;
>      if (!drv)
>          return -ENOMEDIUM;
> -    if (!drv->bdrv_save_vmstate)
> -        return -ENOTSUP;
> -    return drv->bdrv_save_vmstate(bs, buf, pos, size);
> +    if (drv->bdrv_save_vmstate)
> +        return drv->bdrv_save_vmstate(bs, buf, pos, size);
> +    if (bs->file)
> +        return bdrv_save_vmstate(bs->file, buf, pos, size);
> +    return -ENOTSUP;
>  }
>  
>  int bdrv_load_vmstate(BlockDriverState *bs, uint8_t *buf,
> @@ -1694,9 +1696,11 @@ int bdrv_load_vmstate(BlockDriverState *bs, uint8_t *buf,
>      BlockDriver *drv = bs->drv;
>      if (!drv)
>          return -ENOMEDIUM;
> -    if (!drv->bdrv_load_vmstate)
> -        return -ENOTSUP;
> -    return drv->bdrv_load_vmstate(bs, buf, pos, size);
> +    if (drv->bdrv_load_vmstate)
> +        return drv->bdrv_load_vmstate(bs, buf, pos, size);
> +    if (bs->file)
> +        return bdrv_load_vmstate(bs->file, buf, pos, size);
> +    return -ENOTSUP;
>  }
>  
>  void bdrv_debug_event(BlockDriverState *bs, BlkDebugEvent event)
> @@ -1720,20 +1724,37 @@ int bdrv_snapshot_create(BlockDriverState *bs,
>      BlockDriver *drv = bs->drv;
>      if (!drv)
>          return -ENOMEDIUM;
> -    if (!drv->bdrv_snapshot_create)
> -        return -ENOTSUP;
> -    return drv->bdrv_snapshot_create(bs, sn_info);
> +    if (drv->bdrv_snapshot_create)
> +        return drv->bdrv_snapshot_create(bs, sn_info);
> +    if (bs->file)
> +        return bdrv_snapshot_create(bs->file, sn_info);
> +    return -ENOTSUP;
>  }
>  
>  int bdrv_snapshot_goto(BlockDriverState *bs,
>                         const char *snapshot_id)
>  {
>      BlockDriver *drv = bs->drv;
> +    int ret, open_ret;
> +
>      if (!drv)
>          return -ENOMEDIUM;
> -    if (!drv->bdrv_snapshot_goto)
> -        return -ENOTSUP;
> -    return drv->bdrv_snapshot_goto(bs, snapshot_id);
> +    if (drv->bdrv_snapshot_goto)
> +        return drv->bdrv_snapshot_goto(bs, snapshot_id);
> +
> +    if (bs->file) {
> +        drv->bdrv_close(bs);
> +        ret = bdrv_snapshot_goto(bs->file, snapshot_id);
> +        open_ret = drv->bdrv_open(bs, bs->open_flags);
> +        if (open_ret < 0) {
> +            bdrv_delete(bs);

I think you mean bs->file here.

Kevin

> +            bs->drv = NULL;
> +            return open_ret;
> +        }
> +        return ret;
> +    }
> +
> +    return -ENOTSUP;
>  }
>  
>  int bdrv_snapshot_delete(BlockDriverState *bs, const char *snapshot_id)

  reply	other threads:[~2010-05-17 11:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 10:46 [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 1/2] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-12 14:01   ` Christoph Hellwig
2010-05-12 19:50     ` MORITA Kazutaka
2010-05-12 14:28   ` [Qemu-devel] " Avi Kivity
2010-05-12 20:16     ` MORITA Kazutaka
2010-05-13  2:34       ` MORITA Kazutaka
2010-05-12 10:46 ` [Qemu-devel] [RFC PATCH 2/2] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-12 11:38 ` [Qemu-devel] [RFC PATCH 0/2] Sheepdog: distributed storage system for QEMU Kevin Wolf
2010-05-12 19:46   ` MORITA Kazutaka
2010-05-13 14:03     ` MORITA Kazutaka
2010-05-14  8:32       ` Kevin Wolf
2010-05-14  9:54         ` MORITA Kazutaka
2010-05-14 10:05           ` Kevin Wolf
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 0/3] " MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 " MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-17 11:08     ` Kevin Wolf [this message]
2010-05-17 12:19       ` [Qemu-devel] " MORITA Kazutaka
2010-05-17 12:20         ` Kevin Wolf
2010-05-17 13:03           ` MORITA Kazutaka
2010-05-17 10:19   ` [Qemu-devel] [RFC PATCH v3 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 1/3] close all the block drivers before the qemu process exits MORITA Kazutaka
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 2/3] block: call the snapshot handlers of the protocol drivers MORITA Kazutaka
2010-05-14 12:55   ` [Qemu-devel] " Kevin Wolf
2010-05-14  9:51 ` [Qemu-devel] [RFC PATCH v2 3/3] block: add sheepdog driver for distributed storage support MORITA Kazutaka
2010-05-14 11:08   ` [Qemu-devel] " Kevin Wolf
2010-05-17 10:34     ` MORITA Kazutaka

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=4BF12398.2040203@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.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).