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@lists.xensource.com http://lists.xensource.com/xen-devel
> 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''d rather remove the initial mem argument from CREATEDOMAIN, and have the latter just allocate a domid without any actual resources. Come to think of it, we could do away with setdominitialmem as well, and just use setmaxmem and then MEMOP_increase_reservation (which will also return the mfn list you were probably just about to ask for...) Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel