From mboxrd@z Thu Jan 1 00:00:00 1970 From: BVK Chaitanya Subject: Re: [PATCH] serialize suspend-resume process Date: Thu, 31 Jul 2008 18:34:01 +0530 Message-ID: <4891B841.2090901@symantec.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 31/7/08 12:57, "BVK Chaitanya" wrote: >> If dom0 issues second suspend request before resume is completed a _new_ >> kthread is started and will proceed with xen_suspend in parallel. I saw >> this hitting BUG_ON in netfront_accelerator_add_watch. > > That isn't true. xen_suspend() can only be re-entered after it has switched > the 'shutting_down' variable to SHUTDOWN_INVALID. At this point resume work > is completed (except perhaps for resuming some PV devices via xenbus, which > is done asynchronously). > This is the case if suspend is invoked through xenbus interface. With suspend event channel in place, i see that suspend request doesn't go through the shutdown_handler function when suspend is triggered over event channel. regards, -- bvk-chaitanya