WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] earlier remove the backend of tapdisk device in xenstore

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jan Beulich" <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] earlier remove the backend of tapdisk device in xenstore to release the resource allocated in backend driver lies in dom0'kernel
From: "James Song" <jsong@xxxxxxxxxx>
Date: Fri, 23 Apr 2010 03:09:48 -0600
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 23 Apr 2010 02:11:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C7F71EE3.123C4%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4BD172C9020000780003B9E4@xxxxxxxxxxxxxxxxxx> <C7F71EE3.123C4%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


>>> Keir Fraser <keir.fraser@xxxxxxxxxxxxx> 2010-4-23 16:54 >>>
>> 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"
>
> Even though Keir already applied your patch, I continue to disagree:

>>I agreed with you and Jim, and subsequently reverted it.

>> K.
 
Ok, fine, I'll rewrite the patch and send again soon.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel