| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH/RFC] memory_map + set_memmap_limit hypercall/domc
> The fallbacks in XENMEM_memory_map are pointless. Any stable Xen version
> that implements this hypercall will be matched with a corresponding new
> enough tool stack that sets memmap_limit. I think we should continue to
> ENOSYS if memmap_limit has not in fact been specified.
Done.
> The addition of 8MB slack is policy that doesn't belong in Xen. Stick it in
> the top-level caller (XendDomainInfo). In fact it probably belongs in the
> ImnageHandler in image.py, as it's more easily overridden on a per-arch and
> per-image-type basis there.
ImageHandler does not seem to be aware of any distinction between
current memory and the maximum memory a guest can get. Adding it seems
much more work than it requires, so I put it in XenDomainInfo. Is that
okay?
Patch follows soon.
--
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home