From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Shouldn't XendDomainInfo.py: _releaseDevices call destroyDevice? Date: Wed, 16 May 2007 13:33:38 +0100 Message-ID: References: <907625E08839C4409CE5768403633E0B018E1D26@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <907625E08839C4409CE5768403633E0B018E1D26@sefsexmb1.amd.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: "Petersson, Mats" , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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" 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@lists.xensource.com > http://lists.xensource.com/xen-devel