- Timestamp:
- Oct 5, 2018 6:38:24 AM (6 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/VBox/VMM/VMMAll/IEMAllCImplVmxInstr.cpp.h
r74623 r74624 423 423 424 424 /** Check for VMX instructions requiring to be in VMX operation. 425 * @note Any changes here, check if IEMOP_HLP_IN_VMX_OPERATION needs u dpating. */425 * @note Any changes here, check if IEMOP_HLP_IN_VMX_OPERATION needs updating. */ 426 426 #define IEM_VMX_IN_VMX_OPERATION(a_pVCpu, a_szInstr, a_InsDiagPrefix) \ 427 427 do \ … … 825 825 * VINF_SUCCESS is returned). 826 826 * 827 * @remarks Warning! This does not validate the contents of the retr eived segment827 * @remarks Warning! This does not validate the contents of the retrieved segment 828 828 * register. 829 829 */ … … 905 905 * @returns VBox status code. 906 906 * @param pVmcs Pointer to the virtual VMCS. 907 * @param idxCr3Target The index of the CR3-target value to retr eive.907 * @param idxCr3Target The index of the CR3-target value to retrieve. 908 908 * @param puValue Where to store the CR3-target value. 909 909 */ … … 1168 1168 * RIP-relative addressing mode. 1169 1169 * 1170 * The displac ment is 32-bit signed implying an offset range of +/-2G.1170 * The displacement is 32-bit signed implying an offset range of +/-2G. 1171 1171 * See Intel instruction spec. 2.2.1.6 "RIP-Relative Addressing". 1172 1172 */ … … 1796 1796 1797 1797 /** 1798 * Saves the guest force-flags in prepar tion of entering the nested-guest.1798 * Saves the guest force-flags in preparation of entering the nested-guest. 1799 1799 * 1800 1800 * @param pVCpu The cross context virtual CPU structure. … … 1839 1839 1840 1840 /** 1841 * Restores the guest force-flags in prepar tion of exiting the nested-guest.1841 * Restores the guest force-flags in preparation of exiting the nested-guest. 1842 1842 * 1843 1843 * @param pVCpu The cross context virtual CPU structure. … … 5194 5194 * while entering VMX non-root mode. We do some of this while checking VM-execution 5195 5195 * controls. The guest hypervisor should not make assumptions and cannot expect 5196 * predictable behavior if changes to these structures are made in guest memory after5197 * executing VMX non-root mode. As far as VirtualBox is concerned, the guest cannot modify5198 * them anyway as we cache them in host memory. We are trade memory for speed here.5196 * predictable behavior if changes to these structures are made in guest memory while 5197 * executing in VMX non-root mode. As far as VirtualBox is concerned, the guest cannot 5198 * modify them anyway as we cache them in host memory. We are trade memory for speed here. 5199 5199 * 5200 5200 * See Intel spec. 24.11.4 "Software Access to Related Structures".
Note:
See TracChangeset
for help on using the changeset viewer.