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 09:24:11 +0100
Cc:
Delivery-date: Wed, 10 Jun 2009 01:25:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D016DD68C@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+ACOWnyAANCP2iQ==
Thread-topic: [Xen-devel] How to determine memory size in HVM
User-agent: Microsoft-Entourage/12.17.0.090302
On 09/06/2009 08:42, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> memory/target = 786432KB
> XENMEM_current_reservation = 198623 pages
> 
> 198623 << PAGE_SHIFT = 794492KB
> 794492KB - 786432KB = 8060KB
> 
> So I have 8060KB unaccounted for... I guess that's probably the
> framebuffer. According to Device Manager in Windows, the CL5446 device
> uses 64KB of memory at 0xA0000, 32MB at 0xF0000000, and 4KB at
> 0xF3000000. That's more than the extra 8MB, but it would make sense that
> the 32MB wouldn't all be mapped in if it wasn't required.

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.

 -- Keir



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