Is there any range of XEN hypercalls reserved for vendor specific

Is there any range of XEN hypercalls reserved for vendor specific

[veerasena reddy]

[-- Attachment #1.1: Type: text/plain, Size: 547 bytes --]

Hi,

We are looking to add new hypercalls to XEN hypervisor 3.4.3 for one of
projects.
Is there any range of hypercall numbers reserved which can be used to add
new hypercalls any third-party developer other than Xen.
Because if we now add a new hypercall (say, with number #60), and in future
XEN releases a official patch which also adds a new hypercall with same
number (#60), there will be a clash.

So, could you please advice which of the hypercall numbers (may be a range)
can be safely used for our customizations.

Thanks & Regards,
VSR.

[-- Attachment #1.2: Type: text/html, Size: 587 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Is there any range of XEN hypercalls reserved for vendor specific

[Keir Fraser]

On 07/06/2011 07:27, "veerasena reddy" <veeruyours@gmail.com> wrote:

> Hi,
> 
> We are looking to add new hypercalls to XEN hypervisor 3.4.3 for one of
> projects.
> Is there any range of hypercall numbers reserved which can be used to add new
> hypercalls any third-party developer other than Xen.
> Because if we now add a new hypercall (say, with number #60), and in future
> XEN releases a official patch which also adds a new hypercall with same number
> (#60), there will be a clash.
> 
> So, could you please advice which of the hypercall numbers (may be a range)
> can be safely used for our customizations.

No guarantees for out-of-tree extensions, but we allocate hypercall numbers
sequentially, so just pick a big and slightly random starting number and you
shuld be fine (e.g, 0xbcde0000). You'll have to add code to Xen's entry.S to
detect this large number and redirect to your own hypercall_table.

 -- Keir

> Thanks & Regards,
> VSR.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel