WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] How to determine memory size in HVM

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] How to determine memory size in HVM
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 10 Jun 2009 16:07:15 +0300
Cc:
Delivery-date: Wed, 10 Jun 2009 06:07:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D016DD6CC@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnoQyQ+SnpqPcQ3SyyBm4PWOeo0CwAAsYv+ACOWnyAANCP2iQAClQzgAAdNxME=
Thread-topic: [Xen-devel] How to determine memory size in HVM
User-agent: Microsoft-Entourage/12.17.0.090302
On 10/06/2009 12:39, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel