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

Re: [Xen-devel] [PATCH] xen: reserve next two XENMEM_ op numbers for future/out-of-tree use



ping?

> -----Original Message-----
> From: Dan Magenheimer
> Sent: Wednesday, November 28, 2012 3:03 PM
> To: Jan Beulich; Keir Fraser
> Cc: xen-devel@xxxxxxxxxxxxx; Konrad Wilk; Zhigang Wang
> Subject: [PATCH] xen: reserve next two XENMEM_ op numbers for 
> future/out-of-tree use
> 
> xen: reserve next two XENMEM_ op numbers for future/out-of-tree use
> 
> Signed-off-by: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
> 
> diff --git a/xen/include/public/memory.h b/xen/include/public/memory.h
> index f1ddbc0..3ee2902 100644
> --- a/xen/include/public/memory.h
> +++ b/xen/include/public/memory.h
> @@ -421,6 +421,12 @@ struct xen_mem_sharing_op {
>  typedef struct xen_mem_sharing_op xen_mem_sharing_op_t;
>  DEFINE_XEN_GUEST_HANDLE(xen_mem_sharing_op_t);
> 
> +/*
> + * Reserve ops for future/out-of-tree "claim" patches (Oracle)
> + */
> +#define XENMEM_claim_pages                  24
> +#define XENMEM_get_unclaimed_pages          25
> +
>  #endif /* defined(__XEN__) || defined(__XEN_TOOLS__) */
> 
>  #endif /* __XEN_PUBLIC_MEMORY_H__ */

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.