WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH][v2.6.29][XEN] Return unused memory to hyperv

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH][v2.6.29][XEN] Return unused memory to hypervisor
From: Miroslav Rezanina <mrezanin@xxxxxxxxxx>
Date: Fri, 18 Sep 2009 01:02:37 -0400 (EDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 17 Sep 2009 22:03:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <625566043.266451253249879910.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
----- "Jeremy Fitzhardinge" <jeremy@xxxxxxxx> wrote:

> From: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
> To: "Miroslav Rezanina" <mrezanin@xxxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, "Konrad 
> Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
> Sent: Thursday, September 17, 2009 6:47:10 PM GMT +01:00 Amsterdam / Berlin / 
> Bern / Rome / Stockholm / Vienna
> Subject: Re: [Xen-devel] Re: [PATCH][v2.6.29][XEN] Return unused memory to 
> hypervisor
>
> On 09/17/09 01:14, Miroslav Rezanina wrote:
> > Hi Jeremy,
> > I check your application. It won't work correctly. You are calling
> return_unused_memory in xen_memory_setup that is too soon.
> > When you are calling it, there is no hole in map in any case.
> Calling should be in xen_post_allocator_init function (in
> arch/x86/xen/mmu.c).
> >   
> 
> OK.  Where does the e820 map get changed in the meantime?
> 
xen_memory_setup just set RAM map from 0 to initial nr_pages. Only one place 
I'm sure map is changed is
parsing mem parameter. You mentioned that there can be other cases when some 
parts of map are removed.
>     J
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

-- 
Miroslav Rezanina
Software Engineer - Virtualization Team - XEN kernel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel