From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: real physical e820 table for dom0?
Date: Mon, 10 Mar 2014 14:37:57 -0400
Message-ID: <20140310183757.GA11068@phenom.dumpdata.com>
References: <A9667DDFB95DB7438FA9D7D576C3D87E0A9FF00D@SHSMSX104.ccr.corp.intel.com>
	<20140306184507.GB9852@localhost.localdomain>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA0E12B@SHSMSX104.ccr.corp.intel.com>
	<20140307135634.GA9026@phenom.dumpdata.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA10CAF@SHSMSX104.ccr.corp.intel.com>
	<20140310162702.GG4262@phenom.dumpdata.com>
	<531DF8C102000078001227DF@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1WN55W-00057W-8S
	for xen-devel@lists.xenproject.org; Mon, 10 Mar 2014 18:38:10 +0000
Content-Disposition: inline
In-Reply-To: <531DF8C102000078001227DF@nat28.tlf.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>, "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, "'Ian Campbell (Ian.Campbell@citrix.com)'" <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

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.