From mboxrd@z Thu Jan 1 00:00:00 1970 From: "James (song wei)" Subject: Re: earlier remove the backend of tapdisk device in xenstore to release the resource allocated in backend driver lies in dom0'kernel Date: Thu, 22 Apr 2010 20:24:32 -0700 (PDT) Message-ID: <28337027.post@talk.nabble.com> References: <28325456.post@talk.nabble.com> <4BD04B87020000780003B5F4@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BD04B87020000780003B5F4@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Jan Beulich wrote: > > > > >> More generally any solution should be generic, or it should be >> explained properly why the device class needs treatment >> different from any of the other ones (and, for this specific >> case, why moving the device destruction a little ahead will >> now *guarantee* that the cleanup can happen as expected). > > > Moving the device destruction a little ahead of killing qemu-dm would > triger blktapctl thread send CTRMSG_CLOSE to "qemu-dm" before it exit. > And then, qemu-dm would notify backend driver to release resouce by > calling release() of driver through closing the opened device file of > "/dev/xen/blktapN" > > thanks Jim and Jan, > > -James > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > > -- View this message in context: http://old.nabble.com/earlier-remove-the-backend-of-tapdisk-device-in-xenstore-to-release-the-resource-allocated-in-backend-driver-lies-in-dom0%27kernel-tp28325456p28337027.html Sent from the Xen - Dev mailing list archive at Nabble.com.