From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: vmalloc_sync_all() patch problems? Date: Wed, 28 Sep 2011 18:04:49 +0100 Message-ID: <4E8353B1.9070007@citrix.com> References: <4E832F1A.3030209@theshore.net> <4E83330A.3030509@citrix.com> <4E834519.3090300@theshore.net> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E834519.3090300@theshore.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Christopher S. Aker" Cc: xen devel , David Vrabel List-Id: xen-devel@lists.xenproject.org On 28/09/11 17:02, Christopher S. Aker wrote: > On 9/28/11 10:45 AM, David Vrabel wrote: >> You're going to have to provide more information on your system and >> tests I think. > > Nothing crazy. 64 bit Xen, 32 bit dom0, my test suite creates many > domUs (in this case about 40) each with a root image and swap image. > Some swap thrash, some spin cpu, some are repeatedly shut down or xm > destroyed. No networking. This particular box has about 32G in it, and > itself and many other boxes identical to it have no problem with our old > stack (xen 3.4, 2.6.18 dom0). > > I've restarted the tests to see if I can reproduce, but I'm certain that > if it happened once, it'll happen again. Instead of the vmalloc_sync_all() patch you could try this series instead. http://lists.xensource.com/archives/html/xen-devel/2011-09/msg01343.html David