Path: blob/master/include/xen/interface/features.h
10817 views
/******************************************************************************1* features.h2*3* Feature flags, reported by XENVER_get_features.4*5* Copyright (c) 2006, Keir Fraser <[email protected]>6*/78#ifndef __XEN_PUBLIC_FEATURES_H__9#define __XEN_PUBLIC_FEATURES_H__1011/*12* If set, the guest does not need to write-protect its pagetables, and can13* update them via direct writes.14*/15#define XENFEAT_writable_page_tables 01617/*18* If set, the guest does not need to write-protect its segment descriptor19* tables, and can update them via direct writes.20*/21#define XENFEAT_writable_descriptor_tables 12223/*24* If set, translation between the guest's 'pseudo-physical' address space25* and the host's machine address space are handled by the hypervisor. In this26* mode the guest does not need to perform phys-to/from-machine translations27* when performing page table operations.28*/29#define XENFEAT_auto_translated_physmap 23031/* If set, the guest is running in supervisor mode (e.g., x86 ring 0). */32#define XENFEAT_supervisor_mode_kernel 33334/*35* If set, the guest does not need to allocate x86 PAE page directories36* below 4GB. This flag is usually implied by auto_translated_physmap.37*/38#define XENFEAT_pae_pgdir_above_4gb 43940/* x86: Does this Xen host support the MMU_PT_UPDATE_PRESERVE_AD hypercall? */41#define XENFEAT_mmu_pt_update_preserve_ad 54243/* x86: Does this Xen host support the HVM callback vector type? */44#define XENFEAT_hvm_callback_vector 84546/* x86: pvclock algorithm is safe to use on HVM */47#define XENFEAT_hvm_safe_pvclock 94849/* x86: pirq can be used by HVM guests */50#define XENFEAT_hvm_pirqs 105152#define XENFEAT_NR_SUBMAPS 15354#endif /* __XEN_PUBLIC_FEATURES_H__ */555657