Lines Matching refs:VM
63 the VM it is returning to is secure.
152 * SVMs are created from normal VM using (open source) tooling supplied
158 * When the UV_ESM ultracall is made the Ultravisor copies the VM into
389 #. When a normal VM switches to secure mode, all its pages residing
497 #. If the value of the PATE for an existing partition (VM) changes,
502 the PATE entries for a normal VM and can change the PATE entry
665 * U_INVALID if VM is not secure.
703 * U_INVALID if the VM is not secure.
752 * U_INVALID if VM is not secure.
795 * U_INVAL if VM is not secure.
832 * U_SUCCESS on success (including if VM is already secure).
834 * U_INVALID if VM is not secure.
898 * H_STATE if the VM is not in a position to switch to secure.
905 resources in the Ultravisor for the new SVM, transferring the VM's
912 #. Ultravisor uses this hypercall to inform Hypervisor that a VM
938 transition the VM to Secure VM.
976 * H_STATE if called after a VM has gone secure (i.e
980 normal VM).
990 expected to contain the values they had at the time the VM issued
993 the MSR value with which to return to the VM.
996 the VM since the prior ``H_SVM_INIT_START`` hypercall, including paging
998 ``UV_SVM_TERMINATE`` ultracall to terminate the VM.
1000 After the partial state is cleaned up, control returns to the VM
1009 to lack of resources or because the VM's security information could
1012 this virtual machine and return to the VM.
1042 Retrieve the content of the page, belonging to the VM at the specified
1058 #. When a normal VM becomes a secure VM (using the UV_ESM ultracall),
1060 the VM from normal memory to secure memory.