From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: How to determine memory size in HVM
Date: Wed, 10 Jun 2009 16:07:15 +0300
Message-ID: <C6558AB3.7CB3%keir.fraser@eu.citrix.com>
References: <AEC6C66638C05B468B556EA548C1A77D016DD6CC@trantor>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DD6CC@trantor>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: James Harper <james.harper@bendigoit.com.au>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 10/06/2009 12:39, "James Harper" <james.harper@bendigoit.com.au> wrote:

>> Yes, that's the framebuffer. It is variable size, in principle,
> though. I'm
>> not sure you can do better than read XENMEM_current_reservation and
>> memory/target at driver startup time, and keep the delta between them
>> constant.
> 
> There is a XENMEM_maximum_reservation, which I think makes it 8MB
> exactly instead of 8060KB (7.xxxMB). Would I be better off using that as
> a comparison?

I don't think you should depend on that.

Perhaps just having XENMEM_current_reservation track memory/target would be
fine. I'm not sure if it will make e.g. The memory values returned by 'xm
list' incorrect.

We might have to provide more info to you via xenstore to do the 100% right
thing here.

 -- Keir