| rjw | 1f88458 | 2022-01-06 17:20:42 +0800 | [diff] [blame^] | 1 | /* SPDX-License-Identifier: GPL-2.0 */ |
| 2 | /****************************************************************************** |
| 3 | * features.h |
| 4 | * |
| 5 | * Feature flags, reported by XENVER_get_features. |
| 6 | * |
| 7 | * Copyright (c) 2006, Keir Fraser <keir@xensource.com> |
| 8 | */ |
| 9 | |
| 10 | #ifndef __XEN_PUBLIC_FEATURES_H__ |
| 11 | #define __XEN_PUBLIC_FEATURES_H__ |
| 12 | |
| 13 | /* |
| 14 | * If set, the guest does not need to write-protect its pagetables, and can |
| 15 | * update them via direct writes. |
| 16 | */ |
| 17 | #define XENFEAT_writable_page_tables 0 |
| 18 | |
| 19 | /* |
| 20 | * If set, the guest does not need to write-protect its segment descriptor |
| 21 | * tables, and can update them via direct writes. |
| 22 | */ |
| 23 | #define XENFEAT_writable_descriptor_tables 1 |
| 24 | |
| 25 | /* |
| 26 | * If set, translation between the guest's 'pseudo-physical' address space |
| 27 | * and the host's machine address space are handled by the hypervisor. In this |
| 28 | * mode the guest does not need to perform phys-to/from-machine translations |
| 29 | * when performing page table operations. |
| 30 | */ |
| 31 | #define XENFEAT_auto_translated_physmap 2 |
| 32 | |
| 33 | /* If set, the guest is running in supervisor mode (e.g., x86 ring 0). */ |
| 34 | #define XENFEAT_supervisor_mode_kernel 3 |
| 35 | |
| 36 | /* |
| 37 | * If set, the guest does not need to allocate x86 PAE page directories |
| 38 | * below 4GB. This flag is usually implied by auto_translated_physmap. |
| 39 | */ |
| 40 | #define XENFEAT_pae_pgdir_above_4gb 4 |
| 41 | |
| 42 | /* x86: Does this Xen host support the MMU_PT_UPDATE_PRESERVE_AD hypercall? */ |
| 43 | #define XENFEAT_mmu_pt_update_preserve_ad 5 |
| 44 | |
| 45 | /* |
| 46 | * If set, GNTTABOP_map_grant_ref honors flags to be placed into guest kernel |
| 47 | * available pte bits. |
| 48 | */ |
| 49 | #define XENFEAT_gnttab_map_avail_bits 7 |
| 50 | |
| 51 | /* x86: Does this Xen host support the HVM callback vector type? */ |
| 52 | #define XENFEAT_hvm_callback_vector 8 |
| 53 | |
| 54 | /* x86: pvclock algorithm is safe to use on HVM */ |
| 55 | #define XENFEAT_hvm_safe_pvclock 9 |
| 56 | |
| 57 | /* x86: pirq can be used by HVM guests */ |
| 58 | #define XENFEAT_hvm_pirqs 10 |
| 59 | |
| 60 | /* operation as Dom0 is supported */ |
| 61 | #define XENFEAT_dom0 11 |
| 62 | |
| 63 | #define XENFEAT_NR_SUBMAPS 1 |
| 64 | |
| 65 | #endif /* __XEN_PUBLIC_FEATURES_H__ */ |