Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] kexec: Reserve hypercall number

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] kexec: Reserve hypercall number
From: Horms <horms@xxxxxxxxxxxx>
Date: Wed, 30 Aug 2006 14:33:08 +0900
Delivery-date: Wed, 30 Aug 2006 03:18:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060821041110.GA30015@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060821041110.GA30015@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: mutt-ng/devel-r804 (Debian)
On Mon, Aug 21, 2006 at 01:11:12PM +0900, Horms wrote:
> Hi,
> 
> this patch reserves a hypercall number for kexec,
> to ensure that it isn't a moving target.

I notice that since I sent this patch two new hypercall numbers
have been added, __HYPERVISOR_sysctl and __HYPERVISOR_domctl,
but this patch remains neither merged nor nacked.

Is reserving a hypercall number for kexec acceptable?

> kexec: Reserve hypercall number
> 
> This is a micro-excerpt from the kexec patches that
> are being worked on. It just reserves hypercall number 35
> ensure that is isn't a moving target.
> 
> Cc: Magnus Damm <magnus@xxxxxxxxxxxxx>
> Signed-Off-By: Simon Horman <horms@xxxxxxxxxxxx>
> 
> --- 0001/xen/include/public/xen.h
> +++ work/xen/include/public/xen.h     2006-08-21 13:06:15.000000000 +0900
> @@ -61,6 +61,7 @@
>  #define __HYPERVISOR_event_channel_op     32
>  #define __HYPERVISOR_physdev_op           33
>  #define __HYPERVISOR_hvm_op               34
> +#define __HYPERVISOR_kexec_op             35
>  
>  /* Architecture-specific hypercall definitions. */
>  #define __HYPERVISOR_arch_0               48


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel