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

[Xen-devel] DOM0_SETDOMAININITIALMEM


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Michael A Fetterman" <Michael.Fetterman@xxxxxxxxxxxx>
  • Date: Fri, 22 Apr 2005 13:35:47 +0100
  • Delivery-date: Fri, 22 Apr 2005 12:35:29 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVHN89R9nMGH21YQSuOEs0wKNuewA==

Is DOM0_SETDOMAININITIALMEM a deprecated hypercall?

I don't see any evidence of anyone using it in the current unstable tree.

Currently, DOM0_SETDOMAININITIALMEM and DOM0_CREATEDOMAIN
use the function alloc_new_dom_mem() inconsistently with one another,
causing debug-mode builds to crash xen when you attempt to allocate
a domain with more memory than it currently free in the system.

I think the right answer is to kill the DOM0_SETDOMAININITIALMEM
hypercall (if indeed it's not in use), and then fix alloc_new_dom_mem()
to work consistently with DOM0_CREATEDOMAIN.  Right now, it works
consistently with DOM0_SETDOMAININITIALMEM, but that doesn't appear
to have much value if no one is using that hypercall.

Michael


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