direct-io.hg

changeset 15004:3a3ca8da6d4e

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@xensource.com>
author kfraser@localhost.localdomain
date Thu May 03 09:29:07 2007 +0100 (2007-05-03)
parents 2678e31d20f3
children 1cb58c70d813
files xen/include/public/vcpu.h
line diff
     1.1 --- a/xen/include/public/vcpu.h	Wed May 02 09:42:43 2007 -0700
     1.2 +++ b/xen/include/public/vcpu.h	Thu May 03 09:29:07 2007 +0100
     1.3 @@ -161,6 +161,24 @@ DEFINE_XEN_GUEST_HANDLE(vcpu_set_singles
     1.4  #define _VCPU_SSHOTTMR_future (0)
     1.5  #define VCPU_SSHOTTMR_future  (1U << _VCPU_SSHOTTMR_future)
     1.6  
     1.7 +/* 
     1.8 + * Register a memory location in the guest address space for the
     1.9 + * vcpu_info structure.  This allows the guest to place the vcpu_info
    1.10 + * structure in a convenient place, such as in a per-cpu data area.
    1.11 + * The pointer need not be page aligned, but the structure must not
    1.12 + * cross a page boundary.
    1.13 + *
    1.14 + * If the specified mfn is INVALID_MFN, then it reverts to using the
    1.15 + * vcpu_info structure in the shared_info page.
    1.16 + */
    1.17 +#define VCPUOP_register_vcpu_info   10  /* arg == struct vcpu_info */
    1.18 +struct vcpu_register_vcpu_info {
    1.19 +    xen_pfn_t mfn;              /* mfn of page to place vcpu_info */
    1.20 +    uint32_t offset;            /* offset within page */
    1.21 +};
    1.22 +typedef struct vcpu_register_vcpu_info vcpu_register_vcpu_info_t;
    1.23 +DEFINE_XEN_GUEST_HANDLE(vcpu_register_vcpu_info_t);
    1.24 +
    1.25  #endif /* __XEN_PUBLIC_VCPU_H__ */
    1.26  
    1.27  /*