From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with SMTP id A47206B004F for ; Wed, 12 Aug 2009 04:36:02 -0400 (EDT) Message-ID: <4A827EE9.7090102@redhat.com> Date: Wed, 12 Aug 2009 11:35:53 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: Page allocation failures in guest References: <20090713115158.0a4892b0@mjolnir.ossman.eu> <20090811083233.3b2be444@mjolnir.ossman.eu> <4A811545.5090209@redhat.com> <200908121249.51973.rusty@rustcorp.com.au> <20090812081934.33e8280f@mjolnir.ossman.eu> <4A8272B2.3030309@redhat.com> <20090812102225.5a2e2305@mjolnir.ossman.eu> In-Reply-To: <20090812102225.5a2e2305@mjolnir.ossman.eu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Pierre Ossman Cc: Rusty Russell , Minchan Kim , kvm@vger.kernel.org, LKML , linux-mm@kvack.org, Wu Fengguang , KOSAKI Motohiro , Rik van Riel List-ID: On 08/12/2009 11:22 AM, Pierre Ossman wrote: >> >>> Will it still trigger the OOM killer with this patch, or will things >>> behave slightly more gracefully? >>> >>> >> I don't think you mentioned the OOM killer in your original report? Did >> it trigger? >> >> > > I might have things backwards here, but I though the OOM killer started > doing its dirty business once you got that memory allocation failure > dump. > I don't think the oom killer should trigger on GFP_ATOMIC failures, but don't know for sure. If you don't have a trace saying it picked a task to kill, it probably didn't. -- error compiling committee.c: too many arguments to function -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org