[Xen-changelog] [xen-3.1-testing] Even though 3.1.0 won't have an implementation for it, reserve

["Xen patchbot-3.1-testing" <patchbot-3.1-testing@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Date 1178180947 -3600
# Node ID 3a3ca8da6d4e64c41c636055d4014ac5b9fe3ee5
# Parent  2678e31d20f329aaa69c6ba7c9ff32d85f51db4c
Even though 3.1.0 won't have an implementation for it, reserve
VCPUOP_register_vcpu_info anyway so that we can start talking about
the interface on the guest side.

Signed-off-by: Jeremy Fitzhardinge <jeremy@xxxxxxxxxxxxx>
---
 xen/include/public/vcpu.h |   18 ++++++++++++++++++
 1 files changed, 18 insertions(+)

diff -r 2678e31d20f3 -r 3a3ca8da6d4e xen/include/public/vcpu.h
--- a/xen/include/public/vcpu.h Wed May 02 09:42:43 2007 -0700
+++ b/xen/include/public/vcpu.h Thu May 03 09:29:07 2007 +0100
@@ -161,6 +161,24 @@ DEFINE_XEN_GUEST_HANDLE(vcpu_set_singles
 #define _VCPU_SSHOTTMR_future (0)
 #define VCPU_SSHOTTMR_future  (1U << _VCPU_SSHOTTMR_future)
 
+/* 
+ * Register a memory location in the guest address space for the
+ * vcpu_info structure.  This allows the guest to place the vcpu_info
+ * structure in a convenient place, such as in a per-cpu data area.
+ * The pointer need not be page aligned, but the structure must not
+ * cross a page boundary.
+ *
+ * If the specified mfn is INVALID_MFN, then it reverts to using the
+ * vcpu_info structure in the shared_info page.
+ */
+#define VCPUOP_register_vcpu_info   10  /* arg == struct vcpu_info */
+struct vcpu_register_vcpu_info {
+    xen_pfn_t mfn;              /* mfn of page to place vcpu_info */
+    uint32_t offset;            /* offset within page */
+};
+typedef struct vcpu_register_vcpu_info vcpu_register_vcpu_info_t;
+DEFINE_XEN_GUEST_HANDLE(vcpu_register_vcpu_info_t);
+
 #endif /* __XEN_PUBLIC_VCPU_H__ */
 
 /*

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