Orange Pi5 kernel

Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards

3 Commits   0 Branches   0 Tags
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   1) .. SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   2) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   3) ==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   4) Nested VMX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   5) ==========
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   6) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   7) Overview
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   8) ---------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300   9) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  10) On Intel processors, KVM uses Intel's VMX (Virtual-Machine eXtensions)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  11) to easily and efficiently run guest operating systems. Normally, these guests
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  12) *cannot* themselves be hypervisors running their own guests, because in VMX,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  13) guests cannot use VMX instructions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  14) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  15) The "Nested VMX" feature adds this missing capability - of running guest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  16) hypervisors (which use VMX) with their own nested guests. It does so by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  17) allowing a guest to use VMX instructions, and correctly and efficiently
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  18) emulating them using the single level of VMX available in the hardware.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  19) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  20) We describe in much greater detail the theory behind the nested VMX feature,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  21) its implementation and its performance characteristics, in the OSDI 2010 paper
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  22) "The Turtles Project: Design and Implementation of Nested Virtualization",
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  23) available at:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  24) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  25) 	https://www.usenix.org/events/osdi10/tech/full_papers/Ben-Yehuda.pdf
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  26) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  27) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  28) Terminology
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  29) -----------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  30) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  31) Single-level virtualization has two levels - the host (KVM) and the guests.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  32) In nested virtualization, we have three levels: The host (KVM), which we call
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  33) L0, the guest hypervisor, which we call L1, and its nested guest, which we
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  34) call L2.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  35) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  36) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  37) Running nested VMX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  38) ------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  39) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  40) The nested VMX feature is disabled by default. It can be enabled by giving
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  41) the "nested=1" option to the kvm-intel module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  42) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  43) No modifications are required to user space (qemu). However, qemu's default
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  44) emulated CPU type (qemu64) does not list the "VMX" CPU feature, so it must be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  45) explicitly enabled, by giving qemu one of the following options:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  46) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  47)      - cpu host              (emulated CPU has all features of the real CPU)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  48) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  49)      - cpu qemu64,+vmx       (add just the vmx feature to a named CPU type)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  50) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  51) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  52) ABIs
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  53) ----
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  54) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  55) Nested VMX aims to present a standard and (eventually) fully-functional VMX
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  56) implementation for the a guest hypervisor to use. As such, the official
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  57) specification of the ABI that it provides is Intel's VMX specification,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  58) namely volume 3B of their "Intel 64 and IA-32 Architectures Software
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  59) Developer's Manual". Not all of VMX's features are currently fully supported,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  60) but the goal is to eventually support them all, starting with the VMX features
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  61) which are used in practice by popular hypervisors (KVM and others).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  62) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  63) As a VMX implementation, nested VMX presents a VMCS structure to L1.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  64) As mandated by the spec, other than the two fields revision_id and abort,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  65) this structure is *opaque* to its user, who is not supposed to know or care
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  66) about its internal structure. Rather, the structure is accessed through the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  67) VMREAD and VMWRITE instructions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  68) Still, for debugging purposes, KVM developers might be interested to know the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  69) internals of this structure; This is struct vmcs12 from arch/x86/kvm/vmx.c.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  70) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  71) The name "vmcs12" refers to the VMCS that L1 builds for L2. In the code we
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  72) also have "vmcs01", the VMCS that L0 built for L1, and "vmcs02" is the VMCS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  73) which L0 builds to actually run L2 - how this is done is explained in the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  74) aforementioned paper.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  75) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  76) For convenience, we repeat the content of struct vmcs12 here. If the internals
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  77) of this structure changes, this can break live migration across KVM versions.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  78) VMCS12_REVISION (from vmx.c) should be changed if struct vmcs12 or its inner
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  79) struct shadow_vmcs is ever changed.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  80) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  81) ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  82) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  83) 	typedef u64 natural_width;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  84) 	struct __packed vmcs12 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  85) 		/* According to the Intel spec, a VMCS region must start with
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  86) 		 * these two user-visible fields */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  87) 		u32 revision_id;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  88) 		u32 abort;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  89) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  90) 		u32 launch_state; /* set to 0 by VMCLEAR, to 1 by VMLAUNCH */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  91) 		u32 padding[7]; /* room for future expansion */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  92) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  93) 		u64 io_bitmap_a;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  94) 		u64 io_bitmap_b;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  95) 		u64 msr_bitmap;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  96) 		u64 vm_exit_msr_store_addr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  97) 		u64 vm_exit_msr_load_addr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  98) 		u64 vm_entry_msr_load_addr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  99) 		u64 tsc_offset;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) 		u64 virtual_apic_page_addr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) 		u64 apic_access_addr;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) 		u64 ept_pointer;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) 		u64 guest_physical_address;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) 		u64 vmcs_link_pointer;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) 		u64 guest_ia32_debugctl;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) 		u64 guest_ia32_pat;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) 		u64 guest_ia32_efer;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) 		u64 guest_pdptr0;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) 		u64 guest_pdptr1;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) 		u64 guest_pdptr2;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) 		u64 guest_pdptr3;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) 		u64 host_ia32_pat;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) 		u64 host_ia32_efer;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) 		u64 padding64[8]; /* room for future expansion */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) 		natural_width cr0_guest_host_mask;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) 		natural_width cr4_guest_host_mask;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) 		natural_width cr0_read_shadow;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) 		natural_width cr4_read_shadow;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) 		natural_width dead_space[4]; /* Last remnants of cr3_target_value[0-3]. */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) 		natural_width exit_qualification;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) 		natural_width guest_linear_address;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122) 		natural_width guest_cr0;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) 		natural_width guest_cr3;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) 		natural_width guest_cr4;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) 		natural_width guest_es_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) 		natural_width guest_cs_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) 		natural_width guest_ss_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) 		natural_width guest_ds_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) 		natural_width guest_fs_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) 		natural_width guest_gs_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) 		natural_width guest_ldtr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) 		natural_width guest_tr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) 		natural_width guest_gdtr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) 		natural_width guest_idtr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) 		natural_width guest_dr7;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136) 		natural_width guest_rsp;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) 		natural_width guest_rip;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) 		natural_width guest_rflags;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) 		natural_width guest_pending_dbg_exceptions;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) 		natural_width guest_sysenter_esp;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) 		natural_width guest_sysenter_eip;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142) 		natural_width host_cr0;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) 		natural_width host_cr3;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) 		natural_width host_cr4;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) 		natural_width host_fs_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) 		natural_width host_gs_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) 		natural_width host_tr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) 		natural_width host_gdtr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) 		natural_width host_idtr_base;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) 		natural_width host_ia32_sysenter_esp;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) 		natural_width host_ia32_sysenter_eip;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) 		natural_width host_rsp;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) 		natural_width host_rip;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154) 		natural_width paddingl[8]; /* room for future expansion */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) 		u32 pin_based_vm_exec_control;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) 		u32 cpu_based_vm_exec_control;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) 		u32 exception_bitmap;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) 		u32 page_fault_error_code_mask;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) 		u32 page_fault_error_code_match;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) 		u32 cr3_target_count;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) 		u32 vm_exit_controls;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162) 		u32 vm_exit_msr_store_count;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) 		u32 vm_exit_msr_load_count;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) 		u32 vm_entry_controls;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) 		u32 vm_entry_msr_load_count;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) 		u32 vm_entry_intr_info_field;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) 		u32 vm_entry_exception_error_code;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) 		u32 vm_entry_instruction_len;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) 		u32 tpr_threshold;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) 		u32 secondary_vm_exec_control;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) 		u32 vm_instruction_error;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) 		u32 vm_exit_reason;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) 		u32 vm_exit_intr_info;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) 		u32 vm_exit_intr_error_code;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) 		u32 idt_vectoring_info_field;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) 		u32 idt_vectoring_error_code;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) 		u32 vm_exit_instruction_len;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) 		u32 vmx_instruction_info;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) 		u32 guest_es_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) 		u32 guest_cs_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) 		u32 guest_ss_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) 		u32 guest_ds_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) 		u32 guest_fs_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) 		u32 guest_gs_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) 		u32 guest_ldtr_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) 		u32 guest_tr_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) 		u32 guest_gdtr_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) 		u32 guest_idtr_limit;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) 		u32 guest_es_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) 		u32 guest_cs_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) 		u32 guest_ss_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) 		u32 guest_ds_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) 		u32 guest_fs_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) 		u32 guest_gs_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) 		u32 guest_ldtr_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) 		u32 guest_tr_ar_bytes;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) 		u32 guest_interruptibility_info;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) 		u32 guest_activity_state;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) 		u32 guest_sysenter_cs;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) 		u32 host_ia32_sysenter_cs;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) 		u32 padding32[8]; /* room for future expansion */
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) 		u16 virtual_processor_id;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) 		u16 guest_es_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) 		u16 guest_cs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) 		u16 guest_ss_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) 		u16 guest_ds_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) 		u16 guest_fs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) 		u16 guest_gs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) 		u16 guest_ldtr_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) 		u16 guest_tr_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) 		u16 host_es_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) 		u16 host_cs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) 		u16 host_ss_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) 		u16 host_ds_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) 		u16 host_fs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) 		u16 host_gs_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) 		u16 host_tr_selector;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) 	};
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) Authors
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) -------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) These patches were written by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225)     - Abel Gordon, abelg <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226)     - Nadav Har'El, nyh <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227)     - Orit Wasserman, oritw <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228)     - Ben-Ami Yassor, benami <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229)     - Muli Ben-Yehuda, muli <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) With contributions by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232)     - Anthony Liguori, aliguori <at> us.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233)     - Mike Day, mdday <at> us.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234)     - Michael Factor, factor <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235)     - Zvi Dubitzky, dubi <at> il.ibm.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) And valuable reviews by:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238)     - Avi Kivity, avi <at> redhat.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239)     - Gleb Natapov, gleb <at> redhat.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240)     - Marcelo Tosatti, mtosatti <at> redhat.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241)     - Kevin Tian, kevin.tian <at> intel.com
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242)     - and others.