From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: Re: [PATCH] xl.cfg: document the maxmem= option Date: Mon, 7 May 2012 09:37:23 -0700 (PDT) Message-ID: References: <20120504194222.GA28634@phenom.dumpdata.com> <20120504201802.GA16466@aepfle.de> <1336296932.5933.9.camel@cthulhu.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1336296932.5933.9.camel@cthulhu.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Olaf Hering Cc: xen-devel@lists.xensource.com, Konrad Wilk List-Id: xen-devel@lists.xenproject.org > From: Ian Campbell [mailto:Ian.Campbell@citrix.com] > Sent: Sunday, May 06, 2012 3:36 AM > To: Olaf Hering > Cc: xen-devel@lists.xensource.com; Konrad Rzeszutek Wilk > Subject: Re: [Xen-devel] [PATCH] xl.cfg: document the maxmem= option > > On Fri, 2012-05-04 at 16:18 -0400, Olaf Hering wrote: > > On Fri, May 04, Konrad Rzeszutek Wilk wrote: > > > > > On Fri, May 04, 2012 at 09:31:42PM +0200, Olaf Hering wrote: > > > > # HG changeset patch > > > > # User Olaf Hering > > > > # Date 1336159720 -7200 > > > > # Node ID c414728d0d12f1c3e416e40cceefca2f0b00578e > > > > # Parent 8f556a70ae0bef47e242f9e7be0a054769fc8277 > > > > xl.cfg: document the maxmem= option > > > > > > > > Signed-off-by: Olaf Hering > > > > > > > > diff -r 8f556a70ae0b -r c414728d0d12 docs/man/xl.cfg.pod.5 > > > > --- a/docs/man/xl.cfg.pod.5 > > > > +++ b/docs/man/xl.cfg.pod.5 > > > > @@ -484,6 +484,14 @@ are not using hardware assisted paging ( > > > > mode) and your guest workload consists of a a very large number of > > > > similar processes then increasing this value may improve performance. > > > > > > > > +=item B > > > > + > > > > +Specifies the maximum amount of memory the HVM guest can ever see. can _ever_ see... What about guest OS's that support hotplug memory? Also, a subtle point, but is this the maximum physical address that will contain read/write pages or the maximum amount of RAM that the guest OS should be prepared to map as read/writeable (e.g. after subtracting off reserved e820 ranges) or ???