Lines Matching refs:Hypervisor
32 | Hypervisor |
96 | 0 | 1 | 0 | Hypervisor |
105 access secure memory. This means that the Hypervisor cannot access
133 will cause a Hypervisor Emulation Assistance interrupt.
136 memory). An attempt to write to PTCR will cause a Hypervisor
141 Hypervisor Emulation Assistance interrupt.
143 * Paging for an SVM, sharing of memory with Hypervisor for an SVM.
183 with the Ultravisor by a new HMM plug-in in the Hypervisor.
192 Hypervisor.
194 * Normal memory: Memory that is accessible to Hypervisor.
197 Hypervisor.
200 the Hypervisor/QEMU and the SVM (i.e page has mappings in SVM and
201 Hypervisor/QEMU).
220 ultracalls allow the SVMs and Hypervisor to request services from the
241 and Hypervisor. Secure pages that are transferred from secure memory
248 used by Hypervisor and SVMs but others can be added here when it
258 Hypervisor which must handle/fail the calls.
260 Ultracalls used by Hypervisor
264 by the Hypervisor to manage SVMs.
302 Hypervisor in a normal page.
305 scoped page table. But the Hypervisor can provide a hint to the
317 space. In this case, the Hypervisor will allocate a page frame,
323 ``H_SVM_PAGE_OUT`` hypercall to the Hypervisor. The Hypervisor will
328 #. When Hypervisor accesses SVM data, the Hypervisor requests the
330 which the Hypervisor can access. The data in the normal page will
383 The Hypervisor must pin the page in memory before making
392 #. When an SVM requests to share a page with Hypervisor the Hypervisor
396 Ultravisor invokes the Hypervisor to locate the page. After
397 locating the page, the Hypervisor uses UV_PAGE_IN to make the
431 This ultracall informs Ultravisor that the page mapping in Hypervisor
472 * U_PERMISSION if the Hypervisor is attempting to change the PATE
474 context other than Hypervisor.
488 scoped page tables for the Hypervisor as well as each of the
489 virtual machines (both secure and normal). The Hypervisor
493 #. This ultracall allows the Hypervisor to register the partition-
494 scoped and process-scoped page table entries for the Hypervisor
500 #. The Hypervisor is responsible for allocating LPID. The LPID and
501 its PATE entry are registered together. The Hypervisor manages
504 Hypervisor is not allowed to modify them.
509 Return control from the Hypervisor back to the Ultravisor after
511 *reflected*) to the Hypervisor.
523 This call never returns to Hypervisor on success. It returns
524 U_INVALID if ultracall is not made from a Hypervisor context.
531 Hypervisor. After processing the exception, Hypervisor uses the
547 #. Ultravisor relies on the Hypervisor to provide several services to
549 processing the exception, Hypervisor uses UV_RETURN to return
552 #. Hypervisor has to use this ultracall to return control to the SVM.
583 * U_PERMISSION if called from context other than Hypervisor.
598 the Hypervisor move into secure memory. The Hypervisor iterates
600 Ultravisor. Hypervisor may discard some slots such as those used
630 * U_PERMISSION if called from context other than Hypervisor.
666 * U_PERMISSION if not called from a Hypervisor context.
676 #. Called by Hypervisor when terminating an SVM.
685 Share a set of guest physical pages with the Hypervisor.
711 with the Hypervisor. Assume page size is PAGE_SIZE bytes. Zero the
715 back it with an insecure page, with the help of the Hypervisor. If it
723 #. The Hypervisor cannot access the SVM pages since they are backed by
725 pages it can share with Hypervisor.
759 Stop sharing ``num`` pages starting at ``gfn`` with the Hypervisor.
764 and back it with a secure page. Inform the Hypervisor to release
773 #. The SVM may decide to unshare a page from the Hypervisor.
779 Unshare all pages the SVM has shared with Hypervisor.
800 Unshare all shared pages from the Hypervisor. All unshared pages are
802 Hypervisor (using UV_SHARE_PAGE ultracall) are unshared. Ultravisor
803 may internally share some pages with the Hypervisor without explicit
853 Hypervisor Calls API
856 This document describes the Hypervisor calls (hypercalls) that are
858 the Hypervisor to virtual machines and Ultravisor.
875 Hypervisor calls to support Ultravisor
912 #. Ultravisor uses this hypercall to inform Hypervisor that a VM
950 Hypervisor about it. Hypervisor can use this call to finish setting
972 Hypervisor will return this value to the
1010 not be validated, Ultravisor informs the Hypervisor about it.
1011 Hypervisor should use this call to clean up any internal state for
1062 #. Ultravisor uses this hypercall to ask Hypervisor to provide a page
1063 in normal memory that can be shared between the SVM and Hypervisor.
1068 #. If SVM wants to disable sharing of pages with Hypervisor, it can
1070 and inform Hypervisor that it has released access to the normal