[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] earlier remove the backend of tapdisk device in xenstore to release the resource allocated in backend driver lies in dom0'kernel
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@xxxxxxxxxxxxxxxxxxx > 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. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |