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

[Xen-devel] [PATCH 00 of 18] libxc: preparation for hypercall buffers + random cleanups



The following contains some clean ups in preparation for the hypercall
buffer patch series, plus some other bits a bobs which I happened to
notice while preparing that series.

The bulk is adding (and consistently using) specific libxc functions
for each XENMEM_* operation. This allows the memory management in
xc_memory_op to be greatly simplified by converting it to a purely
internal function.

Part of this involved adding variants of
xc_domain_memory_{increase_reservation,decrease_reservation,populate_physmap}
which return the actual number of succesful operations instead of
swallowing partial success and converting to failure.

Rather than add a difficult to detect API change by redefining the
meaning of the integer return value of these types I have instead
introduced new names for these functions in the form of
xc_domain_{increase_reservation,decrease_reservation,populate_physmap}. In
each case I have also added an xc_domain_*_exact variant which
maintains the semantics of the old xc_domain_memory_* functions.

For consistency xc_domain_memory_{set,get}_pod_target have now become
xc_domain_{set,get}_pod_target.

The bits which touch ia64 are not even compile tested since I do not
have access to a suitable userspace-capable cross compiler. However
they are relatively straightforward substitutions.

One patch in the series (#11/18) adds a "# XXX update" suffix to
QEMU_TAG. Rather than applying directly QEMU_TAG should be updated at
this point to include the qemu series posted alongside this one.

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