* The correct way to interact with the version number is similar to\r
* Linux's seqlock: see the implementations of read_seqbegin/read_seqretry.\r
*/\r
- UINT32 version;\r
+ UINT32 Version;\r
UINT32 pad0;\r
- UINT64 tsc_timestamp; /* TSC at last update of time vals. */\r
- UINT64 system_time; /* Time, in nanosecs, since boot. */\r
+ UINT64 TscTimestamp; /* TSC at last update of time vals. */\r
+ UINT64 SystemTime; /* Time, in nanosecs, since boot. */\r
/*\r
* Current system time:\r
* system_time +\r
* CPU frequency (Hz):\r
* ((10^9 << 32) / tsc_to_system_mul) >> tsc_shift\r
*/\r
- UINT32 tsc_to_system_mul;\r
- INT8 tsc_shift;\r
+ UINT32 TscToSystemMultiplier;\r
+ INT8 TscShift;\r
INT8 pad1[3];\r
}; /* 32 bytes */\r
-typedef struct vcpu_time_info vcpu_time_info_t;\r
+typedef struct vcpu_time_info XEN_VCPU_TIME_INFO;\r
\r
struct vcpu_info {\r
/*\r
#endif /* XEN_HAVE_PV_UPCALL_MASK */\r
xen_ulong_t evtchn_pending_sel;\r
struct arch_vcpu_info arch;\r
- struct vcpu_time_info time;\r
+ struct vcpu_time_info Time;\r
}; /* 64 bytes (x86) */\r
#ifndef __XEN__\r
typedef struct vcpu_info vcpu_info_t;\r
* of this structure remaining constant.\r
*/\r
struct shared_info {\r
- struct vcpu_info vcpu_info[XEN_LEGACY_MAX_VCPUS];\r
+ struct vcpu_info VcpuInfo[XEN_LEGACY_MAX_VCPUS];\r
\r
/*\r
* A domain can create "event channels" on which it can send and receive\r
};\r
#ifndef __XEN__\r
typedef struct shared_info shared_info_t;\r
+typedef struct shared_info XEN_SHARED_INFO;\r
#endif\r
\r
/* Turn a plain number into a C UINTN constant. */\r