From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 5/7] migration: omit drive ref as we have bdrv_ref now
Date: Fri, 02 Aug 2013 16:13:55 +0800 [thread overview]
Message-ID: <51FB6A43.1050108@linux.vnet.ibm.com> (raw)
In-Reply-To: <1375265640-27307-6-git-send-email-famz@redhat.com>
There should be a section of code in device hot unplug, checking
DriverInfo's ref, fail or do nothing when ref != 1. But I haven't found
that code, so not sure whether this patch will change the behavior in
device hot unplug.
> block-migration.c does not actually use DriveInfo anywhere. Hence it's
> safe to drive ref code, we really only care about referencing BDS.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> block-migration.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block-migration.c b/block-migration.c
> index f803f20..daf9ec1 100644
> --- a/block-migration.c
> +++ b/block-migration.c
> @@ -336,8 +336,8 @@ static void init_blk_migration_it(void *opaque, BlockDriverState *bs)
> bmds->completed_sectors = 0;
> bmds->shared_base = block_mig_state.shared_base;
> alloc_aio_bitmap(bmds);
> - drive_get_ref(drive_get_by_blockdev(bs));
> bdrv_set_in_use(bs, 1);
> + bdrv_ref(bs);
>
> block_mig_state.total_sector_sum += sectors;
>
> @@ -575,7 +575,7 @@ static void blk_mig_cleanup(void)
> while ((bmds = QSIMPLEQ_FIRST(&block_mig_state.bmds_list)) != NULL) {
> QSIMPLEQ_REMOVE_HEAD(&block_mig_state.bmds_list, entry);
> bdrv_set_in_use(bmds->bs, 0);
> - drive_put_ref(drive_get_by_blockdev(bmds->bs));
> + bdrv_unref(bmds->bs);
> g_free(bmds->aio_bitmap);
> g_free(bmds);
> }
>
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2013-08-02 8:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 10:13 [Qemu-devel] [PATCH v3 0/7] Implement reference count for BlockDriverState Fam Zheng
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 1/7] vvfat: use bdrv_new() to allocate BlockDriverState Fam Zheng
2013-08-02 7:23 ` Wenchao Xia
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 2/7] iscsi: use bdrv_new() instead of stack structure Fam Zheng
2013-08-02 7:34 ` Wenchao Xia
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 3/7] block: implement reference count for BlockDriverState Fam Zheng
2013-08-02 7:36 ` Wenchao Xia
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 4/7] block: make bdrv_delete() static Fam Zheng
2013-08-02 7:40 ` Wenchao Xia
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 5/7] migration: omit drive ref as we have bdrv_ref now Fam Zheng
2013-08-02 8:13 ` Wenchao Xia [this message]
2013-08-02 15:04 ` Stefan Hajnoczi
2013-07-31 10:13 ` [Qemu-devel] [PATCH v3 6/7] xen_disk: simplify blk_disconnect with refcnt Fam Zheng
2013-08-02 8:24 ` Wenchao Xia
2013-07-31 10:14 ` [Qemu-devel] [PATCH v3 7/7] nbd: use BlockDriverState refcnt Fam Zheng
2013-08-02 8:28 ` Wenchao Xia
2013-08-01 12:23 ` [Qemu-devel] [PATCH v3 0/7] Implement reference count for BlockDriverState Stefan Hajnoczi
2013-08-01 12:28 ` Stefan Hajnoczi
2013-08-02 2:22 ` Fam Zheng
2013-08-02 15:06 ` Stefan Hajnoczi
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=51FB6A43.1050108@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).