qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, pbonzini@redhat.com,
	xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend]
Date: Fri, 23 Aug 2013 09:01:04 +0800	[thread overview]
Message-ID: <20130823010104.GA2484@T430s.nay.redhat.com> (raw)
In-Reply-To: <20130822113810.GA27613@stefanha-thinkpad.redhat.com>

On Thu, 08/22 13:38, Stefan Hajnoczi wrote:
> On Fri, Aug 09, 2013 at 06:01:53PM +0800, Fam Zheng wrote:
> > [resend to the correct list]
> > 
> > BlockDriverState lifecycle management is needed by future features such as
> > image fleecing and blockdev-add. This series adds reference count to
> > BlockDriverState.
> > 
> > The first two patches clean up two odd BlockDriverState use cases, so all code
> > uses bdrv_new() to create BlockDriverState instance.
> > 
> > Then implemented bdrv_ref() and bdrv_unref() to operate on refcnt: Initially,
> > refcnt is 1, which means bdrv_unref is effectively a bdrv_delete() here. So
> > patch 04 has a search and replace to convert bdrv_delete to bdrv_unref, before
> > bdrv_ref is used anywhere. 05~08 patches calls bdrv_ref for device attach,
> > block-migration and nbd.
> > 
> > The rule is: Either bdrv_ref() or bdrv_new() must have a matching
> > bdrv_unref() call, and the last matching bdrv_unref deletes the bs.
> > 
> > v4:
> >     08: Added, let block job use BDS reference.
> >     02: Fix leak of bs.opaque
> > 
> > v3:
> >     03: Removed unnecessary bdrv_close() call.
> > 
> > v2:
> >     05: Removed: "block: use BlockDriverState refcnt for device attach/detach"
> >     07: Fix xen_disk blk_disconnect() as it depended on device attach refcnt.
> 
> Sorry, can't merge this because it breaks qemu-iotests 041 and 055:
> 
>   $ ./check -qcow2 055 041

041 works for me, so I will post v6 to fix 055. If 041 still not working
then, I'll look into it.
> 
> Please always run qemu-iotests before submitting patches.
> 
OK.

Thanks

Fam

  reply	other threads:[~2013-08-23  1:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 10:01 [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend] Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 1/8] vvfat: use bdrv_new() to allocate BlockDriverState Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 2/8] iscsi: use bdrv_new() instead of stack structure Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 3/8] block: implement reference count for BlockDriverState Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 4/8] block: make bdrv_delete() static Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 5/8] migration: omit drive ref as we have bdrv_ref now Fam Zheng
2013-08-09 10:01 ` [Qemu-devel] [PATCH v5 6/8] xen_disk: simplify blk_disconnect with refcnt Fam Zheng
2013-08-09 10:02 ` [Qemu-devel] [PATCH v5 7/8] nbd: use BlockDriverState refcnt Fam Zheng
2013-08-09 10:02 ` [Qemu-devel] [PATCH v5 8/8] block: use BDS ref for block jobs Fam Zheng
2013-08-22 11:38 ` [Qemu-devel] [PATCH v5 0/8] Implement reference count for BlockDriverState [resend] Stefan Hajnoczi
2013-08-23  1:01   ` Fam Zheng [this message]
2013-08-23  2:17   ` Wenchao Xia
2013-08-26  7:40     ` 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=20130823010104.GA2484@T430s.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=xiawenc@linux.vnet.ibm.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).