[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Wed, 10 Jun 2009 19:39:19 +1000
  • Cc:
  • Delivery-date: Wed, 10 Jun 2009 02:39:46 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcnoQyQ+SnpqPcQ3SyyBm4PWOeo0CwAAsYv+ACOWnyAANCP2iQAClQzg
  • Thread-topic: [Xen-devel] How to determine memory size in HVM

> >
> > 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.
> 

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?

James

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.