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] Shouldn't XendDomainInfo.py: _releaseDevices call destro

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Shouldn't XendDomainInfo.py: _releaseDevices call destroyDevice?
From: Tom Wilkie <tom.wilkie@xxxxxxxxx>
Date: Wed, 16 May 2007 13:37:26 +0100
Cc: "Petersson, Mats" <Mats.Petersson@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Tom Wilkie <tom.wilkie@xxxxxxxxx>
Delivery-date: Wed, 16 May 2007 05:35:47 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=jhfU3NqEii+1+Cf7p/SkakDjhdLxf5ydEGxFInYlb4otPmDtsm5lzuXG178UfaGk7J1E/di7T/u8BXsQ2OUXRPOoA6d1bcAKHYcoFMlTr0VwK9/ZGiwlQsR+i+R4y0AjuEtcnKAb3lu2Q43ibgJcEw7a1UieVKzbJGjzy1rkebc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=p6icqt00+TlS9Kro6ixDJwYrgXGUilpIf/yABzj2jJI72FqPhubeLxErb+V5CVIeFKaXF/Hsj9w0UkMY3xJ91PY/wbC7b75ER/U6QpL5vWuFsPcuZ+0kCxkqdos1noCa9O1QNo2Hd6i5MG4riDST1hDodFoz5is/6b6z9SpF1YA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C270B8B2.F062%keir@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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C270B8B2.F062%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
It would make sense, I was going to give it a test but never got round to it. Feel free to try it out

Tom

On 16 May 2007, at 13:33, Keir Fraser wrote:

This is how it looks to me too! Unless Ewan or Tom knows better, this is probably worth trying out. It would be a neater solution for the console
backend cleanup than your hacky patch, if it works.

 -- Keir

On 16/5/07 13:04, "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:

It seems like something is missing in the _releaseDevices, and I think the correct way to fix it would be to call destroyDevice - is there any reason I shouldn't use that function, rather than the current method of
removing (some of) the device info from XenStore in _releaseDevices?

--
Mats



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


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


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