From mboxrd@z Thu Jan 1 00:00:00 1970 From: Murillo Fernandes Bernardes Subject: Re: [PATCH] Fix device removal on net and block frontend drivers Date: Mon, 21 Nov 2005 14:33:31 -0200 Message-ID: <200511211433.31356.mfb@br.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Monday 21 November 2005 14:07, Stefan Berger wrote: > xen-devel-bounces@lists.xensource.com wrote on 11/21/2005 10:43:01 AM: > > Frontend devices are not being unregistered when in closed state. The > > following patch fix that. > > > > Fix bug #420. > > > > Makes "05_attach_and_dettach_device_repeatedly_pos" and > > "09_attach_and_dettach_device_check_data_pos" tests pass. > > Did you test this with suspending / resuming a dom U? The reason I am > asking is that when suspending the driver immediately gets into state > 'Closed' and when resuming into state 'Connected', but now your device is > unregistered. No, I did not test suspend/resume. I really don't see why it should get into Closed on suspend, but anyway, is this really hapenning? I could not find any switch to Closed into suspend's code, neither on resume. How to test suspend/resume on a domU? It does not have /sys/power/state neither /proc/sleep. -- Murillo Fernandes Bernardes IBM Linux Technology Center