1 /******************************************************************************
4 * Feature flags, reported by XENVER_get_features.
6 * Copyright (c) 2006, Keir Fraser <keir@xensource.com>
9 #ifndef __XEN_PUBLIC_FEATURES_H__
10 #define __XEN_PUBLIC_FEATURES_H__
13 * If set, the guest does not need to write-protect its pagetables, and can
14 * update them via direct writes.
16 #define XENFEAT_writable_page_tables 0
19 * If set, the guest does not need to write-protect its segment descriptor
20 * tables, and can update them via direct writes.
22 #define XENFEAT_writable_descriptor_tables 1
25 * If set, translation between the guest's 'pseudo-physical' address space
26 * and the host's machine address space are handled by the hypervisor. In this
27 * mode the guest does not need to perform phys-to/from-machine translations
28 * when performing page table operations.
30 #define XENFEAT_auto_translated_physmap 2
32 /* If set, the guest is running in supervisor mode (e.g., x86 ring 0). */
33 #define XENFEAT_supervisor_mode_kernel 3
36 * If set, the guest does not need to allocate x86 PAE page directories
37 * below 4GB. This flag is usually implied by auto_translated_physmap.
39 #define XENFEAT_pae_pgdir_above_4gb 4
41 /* x86: Does this Xen host support the MMU_PT_UPDATE_PRESERVE_AD hypercall? */
42 #define XENFEAT_mmu_pt_update_preserve_ad 5
45 * If set, GNTTABOP_map_grant_ref honors flags to be placed into guest kernel
48 #define XENFEAT_gnttab_map_avail_bits 7
50 /* x86: Does this Xen host support the HVM callback vector type? */
51 #define XENFEAT_hvm_callback_vector 8
53 /* x86: pvclock algorithm is safe to use on HVM */
54 #define XENFEAT_hvm_safe_pvclock 9
56 /* x86: pirq can be used by HVM guests */
57 #define XENFEAT_hvm_pirqs 10
59 /* operation as Dom0 is supported */
60 #define XENFEAT_dom0 11
62 #define XENFEAT_NR_SUBMAPS 1
64 #endif /* __XEN_PUBLIC_FEATURES_H__ */