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

[Xen-devel] PoD, 4.2, and current/maximum reservation


  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: James Harper <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Mon, 11 Feb 2013 00:03:34 +0000
  • Accept-language: en-AU, en-US
  • Delivery-date: Mon, 11 Feb 2013 00:04:13 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac4H6swD3JGQERAlREGi/33A8IBUgA==
  • Thread-topic: PoD, 4.2, and current/maximum reservation

A user has pointed out a problem with GPLPV under Xen 4.2 when using PoD. I'm 
using the difference between XENMEM_maximum_reservation and 
XENMEM_current_reservation to tell me how much I should balloon down to account 
for PoD, but when the user has ballooned down to 1G (from 4Gb or 8GB), GPLPV 
logs the following:

13005008825593: XenPCI     XENMEM_maximum_reservation = 262400
13005008825593: XenPCI     XENMEM_current_reservation = 262136
13005008825609: XenPCI     Trying to give 1056 KB (1 MB) to Xen

What is the correct way to tell how much PoD memory there is under 4.2? Am I 
doing it wrong?

I balloon down as early as possible (before xenbus starts) to avoid windows 
going over its limit so I'm hoping I can determine the size of PoD memory just 
via hypercalls.

Thanks

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

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