[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH V15 5/9] xen: Make gpfn related memops compatible with wider return values
On 20/04/15 16:06, Tamas K Lengyel wrote: > The current implementation of three memops, XENMEM_current_reservation, > XENMEM_maximum_reservation and XENMEM_maximum_gpfn return values as an > int. However, in ARM64 we could potentially have 36-bit pfn's, thus > in preparation for the ARM patch, in this patch we update the existing > memop routines to use a struct, xen_get_gpfn, to exchange the gpfn info > as a uin64_t. > > This patch also adds error checking on the toolside in case the memop > fails. > > Signed-off-by: Tamas K Lengyel <tklengyel@xxxxxxxxxxxxx> XENMEM, unlikely domctls/sysctls is a guest-visible stable ABI/API. You cannot make adjustments like this, but you can add a brand new op with appropriate parameters and list the old ops as deprecated. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |