Documentation/powerpc/ultravisor.rst

44     random values in the SVM.
62       to return to a SVM it must use an ultracall. It can determine if
106       the memory of the SVM without using an ultracall (asking the
108       the SVM memory encrypted.
113     * The architecture allows the SVM to share pages of memory with the
115       sharing must be initiated by the SVM.
143       * Paging for an SVM, sharing of memory with Hypervisor for an SVM.
160       integrity of the SVM. If the integrity check passes the Ultravisor
164       encrypted disk associated with the SVM. This pass phrase is given
165       to the SVM when requested.
168       the SVM while at rest.
170     * For external interrupts the Ultravisor saves the state of the SVM,
179     * The Ultravisor uses AES (IAPM) for protection of SVM memory. IAPM
200       the Hypervisor/QEMU and the SVM (i.e page has mappings in SVM and
207       Ultravisor and SVM.
209     * SVM: Secure Virtual Machine.
219     support Secure Virtual Machines (SVM)s and Paravirtualized KVM. The
304     By default, the source page is unmapped from the SVM's partition-
315     #. QEMU attempts to access an address belonging to the SVM but the
328     #. When Hypervisor accesses SVM data, the Hypervisor requests the
372     partition-scoped page-table of the SVM.  If `dest_gpa` is not shared,
392     #. When an SVM requests to share a page with Hypervisor the Hypervisor
395     #. When an SVM accesses a secure page that has been paged-out,
503        anytime. Ultravisor manages the PATE entries for an SVM and
529     When an SVM makes an hypercall or incurs some other exception, the
532     ``UV_RETURN`` ultracall to return control back to the SVM.
548        the SVM such as processing hypercall and other exceptions. After
552     #. Hypervisor has to use this ultracall to return control to the SVM.
558     Register an SVM address-range with specified properties.
566 		uint64_t lpid,		/* LPAR ID of the SVM */
590     Register a memory range for an SVM.  The memory range starts at the
609     Unregister an SVM address-range that was previously registered using
618 		uint64_t lpid,		/* LPAR ID of the SVM */
647     Terminate an SVM and release its resources.
655 		uint64_t lpid,		/* LPAR ID of the SVM */)
671     Terminate an SVM and release all its resources.
676     #. Called by Hypervisor when terminating an SVM.
679 Ultracalls used by SVM
723     #. The Hypervisor cannot access the SVM pages since they are backed by
724        secure pages. Hence an SVM must explicitly request Ultravisor for
734     Restore a shared SVM page to its initial state.
773     #. The SVM may decide to unshare a page from the Hypervisor.
779     Unshare all pages the SVM has shared with Hypervisor.
801     zeroed on return. Only pages explicitly shared by the SVM with the
804     request from the SVM.  These pages will not be unshared by this
811        kernel. It may also be needed during SVM reset.
838 	* U_RETRY	insufficient memory to create SVM.
883     Begin the process of converting a normal virtual machine into an SVM.
905     resources in the Ultravisor for the new SVM, transferring the VM's
919     Complete the process of securing an SVM.
935 				from an SVM or before an H_SVM_INIT_START
957     Abort the process of securing an SVM.
1063        in normal memory that can be shared between the SVM and Hypervisor.
1066        can happen when the SVM touches a paged-out page.
1068     #. If SVM wants to disable sharing of pages with Hypervisor, it can