All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Philipson <Ross.Philipson@citrix.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: James McKenzie <James.McKenzie@citrix.com>
Subject: [PATCH 1/1] Reserve V4V hypercall number
Date: Wed, 13 Jul 2011 11:03:09 -0400	[thread overview]
Message-ID: <831D55AF5A11D64C9B4B43F59EEBF720724926C135@FTLPMAILBOX02.citrite.net> (raw)


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

Reserve the V4V hypercall number to prevent its use prior to the up-streaming of the rest of the V4V functionality.



Signed-off-by: Ross Philipson <ross.philipson@citrix.com<mailto:ross.philipson@citrix.com>>


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

[-- Attachment #2: v4v-hypercall-number.patch --]
[-- Type: application/octet-stream, Size: 472 bytes --]

diff -r 00d2c5ca26fd xen/include/public/xen.h
--- a/xen/include/public/xen.h	Fri Jul 08 18:35:24 2011 +0100
+++ b/xen/include/public/xen.h	Wed Jul 13 10:48:46 2011 -0400
@@ -93,6 +93,7 @@
 #define __HYPERVISOR_domctl               36
 #define __HYPERVISOR_kexec_op             37
 #define __HYPERVISOR_tmem_op              38
+#define __HYPERVISOR_v4v_op               39
 
 /* Architecture-specific hypercall definitions. */
 #define __HYPERVISOR_arch_0               48

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

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

             reply	other threads:[~2011-07-13 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 15:03 Ross Philipson [this message]
2011-07-13 15:24 ` [PATCH 1/1] Reserve V4V hypercall number Tim Deegan
2011-07-13 15:27   ` Ross Philipson

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=831D55AF5A11D64C9B4B43F59EEBF720724926C135@FTLPMAILBOX02.citrite.net \
    --to=ross.philipson@citrix.com \
    --cc=James.McKenzie@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.