From: Ian Campbell Subject: Re: [PATCH] Disallow setting maxmem to higher value than total physical memory size Date: Thu, 2 Sep 2010 06:43:20 +0100 Message-ID: <1283406200.3469.143.camel@localhost.localdomain> References: <4C7E47B2.9010805@redhat.com> <1283345049.12544.9494.camel@zakaz.uk.xensource.com> <4C7E8523.2080108@goop.org> <1283363785.3469.104.camel@localhost.localdomain> <4C7E9833.4070106@goop.org> <1283367212.3469.136.camel@localhost.localdomain> <4C7EC13D.2040905@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C7EC13D.2040905@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Michal Novotny , "'xen-devel@lists.xensource.com'" List-Id: xen-devel@lists.xenproject.org On Wed, 2010-09-01 at 22:10 +0100, Jeremy Fitzhardinge wrote: > > > It's not only in xenstore, it is also in the result of the > > XENMEM_get_memory_map hypercall. > > Is that separate from 3? As far as the h/v is concerned yes. Although they know it's an e820 the set/get_memory_map hypercalls basically store an opaque blob so far as the h/v is concerned. xend doesn't seem so sure they are unrelated... > > Old-style PV Linux domains really do use static-max in this way. It may > > well be that there are potentially better ways for guests to implement > > this in the future but we have a deployed base of guests which work this > > way. > > I specifically meant the Xenstore "static-max" value is useless. > Getting it via hypercall is fine. I'm not sure but I think this is used by HVM balloon drivers when PoD is active. I don't know why this is the case though, other than XENMEM_get_memory_map being a PV only hypercall. Ian.