From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Wroblewski Subject: Re: [PATCH v2] Fix scheduler crash after s3 resume Date: Fri, 25 Jan 2013 11:29:49 +0100 Message-ID: <51025E9D.1000403@citrix.com> References: <5100070F.7010808@citrix.com> <5100D229.4030906@ts.fujitsu.com> <510144A3.9060302@citrix.com> <5101630D02000078000B93AD@nat28.tlf.novell.com> <51016065.3080902@citrix.com> <510175E802000078000B94A1@nat28.tlf.novell.com> <51024B56.20706@citrix.com> <5102603302000078000B985C@nat28.tlf.novell.com> <5102541D.1070408@citrix.com> <5102694B02000078000B98B7@nat28.tlf.novell.com> <51025D2C.3040005@ts.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51025D2C.3040005@ts.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Juergen Gross Cc: George Dunlap , "Keir (Xen.org)" , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 25/01/13 11:23, Juergen Gross wrote: > What about adding a global scheduler_disable() in freeze_domains() and a > scheduler_enable() in thaw_domains() which will switch scheduler locking to > a global lock (or disable it at all?). This should solve all problems without > any complex changes of current behavior. > > Yes, I'd be very happy to test such a patch! Probably not familiar enough with this to be able to write the disable/enable logic myself though