: Re: [Qemu-devel] [PATCH v2] Do not delete BlockDriverState when
deleting the drive
Date: Tue, 22 Mar 2011 20:53:47 -0500
Message-ID: 20110323015347.ga20...@us.ibm.com
User-Agent: Mutt/1.5.6+20040907i
To: Markus Armbruster arm...@redhat.com
Cc: Kevin Wolf kw...@redhat.com, Ryan
* Markus Armbruster arm...@redhat.com [2011-03-24 07:27]:
Whoops, almost missed this. Best to cc: me to avoid that.
It was sent directly to you:
Sender: qemu-devel-bounces+ryanh=us.ibm@nongnu.org
From: Ryan Harper ry...@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] Do
Whoops, almost missed this. Best to cc: me to avoid that.
Ryan Harper ry...@us.ibm.com writes:
* Markus Armbruster arm...@redhat.com [2011-03-15 04:48]:
Sorry for the long delay, I was out of action for a week.
Ryan Harper ry...@us.ibm.com writes:
When removing a drive from the
* Markus Armbruster arm...@redhat.com [2011-03-15 04:48]:
Sorry for the long delay, I was out of action for a week.
Ryan Harper ry...@us.ibm.com writes:
When removing a drive from the host-side via drive_del we currently have the
following path:
drive_del
qemu_aio_flush()
Sorry for the long delay, I was out of action for a week.
Ryan Harper ry...@us.ibm.com writes:
When removing a drive from the host-side via drive_del we currently have the
following path:
drive_del
qemu_aio_flush()
bdrv_close()
drive_uninit()
bdrv_delete()
When we bdrv_delete() we end
When removing a drive from the host-side via drive_del we currently have the
following path:
drive_del
qemu_aio_flush()
bdrv_close()
drive_uninit()
bdrv_delete()
When we bdrv_delete() we end up qemu_free() the BlockDriverState pointer
however, the block devices retain a copy of this pointer, see
