From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: cannot access memory beyond end of bootstrap direct-map area Date: Fri, 28 Aug 2009 07:38:08 +0100 Message-ID: References: <42DFDE8E-15DB-434C-8AD1-87981E05AAD2@gandi.net> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <42DFDE8E-15DB-434C-8AD1-87981E05AAD2@gandi.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: Pascal Bouchareine Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 27/08/2009 22:41, "Pascal Bouchareine" wrote: >> You should be able to remove the bogus move_memory() call, and change >> absolutely nothing else. Does that also work for you? That's the >> change I >> would check in. > > Yup, I thought that's what the patch did, modulo we need to keep track > of initial_images_start > and need "e" in place for the loop ? Or I need a look at the original > fix. Initial_images_start and e would already be correct for the loop. Just the move_memory() call outside the loop is completely unnecessary. Try removing just that call and see if that works. -- Keir