From: veerasena reddy <veeruyours@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Is there any range of XEN hypercalls reserved for vendor specific
Date: Tue, 7 Jun 2011 11:57:23 +0530 [thread overview]
Message-ID: <BANLkTim5A0tAPAgtbSAy4MNQxo8JXjipXA@mail.gmail.com> (raw)
[-- 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
next reply other threads:[~2011-06-07 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 6:27 veerasena reddy [this message]
2011-06-07 7:02 ` Is there any range of XEN hypercalls reserved for vendor specific Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTim5A0tAPAgtbSAy4MNQxo8JXjipXA@mail.gmail.com \
--to=veeruyours@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).