From: Jeremy Fitzhardinge Subject: Re: [Xen-devel] Re: [PATCH 0/6] xen: don't call vmalloc_sync_all() when mapping foreign pages Date: Wed, 21 Sep 2011 11:57:24 -0700 Message-ID: <4E7A3394.3090806@goop.org> References: <1316090411-22608-1-git-send-email-david.vrabel@citrix.com> <4E727017.4030001@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Stefano Stabellini Cc: "linux-kernel@vger.kernel.org" , Andrew Morton , "xen-devel@lists.xensource.com" , David Vrabel , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 09/21/2011 03:42 AM, Stefano Stabellini wrote: > On Thu, 15 Sep 2011, Jeremy Fitzhardinge wrote: >> This series is relying on regular ram mappings are already synced to all >> tasks, but I'm not sure that's necessarily guaranteed (for example, if >> you hotplug new memory into the domain, the new pages won't be mapped >> into every mm unless they're synced). > the series is using GFP_KERNEL, so this problem shouldn't occur, right? What properties do you think GFP_KERNEL guarantees? J