Re: real physical e820 table for dom0?

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Mon, Mar 10, 2014 at 04:39:13PM +0000, Jan Beulich wrote:
> >>> On 10.03.14 at 17:27, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Mon, Mar 10, 2014 at 08:22:48AM +0000, Zhang, Yang Z wrote:
> >> Konrad Rzeszutek Wilk wrote on 2014-03-07:
> >> > On Fri, Mar 07, 2014 at 01:29:31AM +0000, Zhang, Yang Z wrote:
> >> > 
> >> > How do you use the dom0_mem_max= argument? And what version of Xen are
> >> > you using?
> >> > 
> >> 
> >> I tried it both in Xen and dom0, no help. But adding 
> > "dom0_mem=4096M,max:4096M" to xen cmdline helps.
> >> I am using the latest Xen upstream.
> > 
> > Right. That is how it is suppose to work. What did you have before?
> > dom0_mem=4G?
> > 
> > That means it will boot with all the memory that Xen sees and balloon down 
> > to 4GB.
> 
> Since when?

I was thinking this would be it:
8f370c14acf1c326a5e0ab8c505414600ff3c0
Author: David Vrabel <david.vrabel@citrix.com>
Date:   Mon Aug 22 10:05:27 2011 +0100

    x86: use 'dom0_mem' to limit the number of pages for dom0
    
    Use the 'dom0_mem' command line option to set the maximum number of
    pages for dom0.  dom0 can use then use the XENMEM_maximum_reservation
    memory op to automatically find this limit and reduce the size of any
    page tables etc.
   
But now that I look at the code, I see that if you specific
dom0_mem=4G it will boot with 4GB and no more.


And the Linux kernel should be able to work with that.