Lines Matching +full:use +full:- +full:cases
1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
62 to return to a SVM it must use an ultracall. It can determine if
75 +---+---+---+---------------+
79 +---+---+---+---------------+
81 +---+---+---+---------------+
83 +---+---+---+---------------+
85 +---+---+---+---------------+
89 +---+---+---+---------------+
93 +---+---+---+---------------+
95 +---+---+---+---------------+
97 +---+---+---+---------------+
99 +---+---+---+---------------+
139 * LDBAR (LD Base Address Register) and IMC (In-Memory Collection)
140 non-architected registers. An attempt to write to them will cause a
183 with the Ultravisor by a new HMM plug-in in the Hypervisor.
222 be accessed when running in Ultravisor-privileged mode.
237 parameter-position based code. i.e U_PARAMETER, U_P2, U_P3 etc
267 -----------
275 .. code-block:: c
280 uint64_t src_gpa, /* source guest-physical-address */
296 * U_BUSY if page cannot be currently paged-out.
301 Encrypt the contents of a secure-page and make it available to
304 By default, the source page is unmapped from the SVM's partition-
312 Use cases
321 #. When Ultravisor runs low on secure memory and it needs to page-out
334 ----------
341 .. code-block:: c
356 * U_BUSY if page cannot be currently paged-in.
372 partition-scoped page-table of the SVM. If `dest_gpa` is not shared,
386 Use cases
395 #. When an SVM accesses a secure page that has been paged-out,
401 -------------
408 .. code-block:: c
412 uint64_t guest_pa, /* destination guest-physical-address */
437 Use cases
441 because it is paged-out to disk, Ultravisor needs to know that the
446 -------------
454 .. code-block:: c
479 Validate and write a LPID and its partition-table-entry for the given
483 Use cases
487 called PATE (Partition Table Entries), point to the partition-
490 operates in partition 0 and its partition-scoped page tables
493 #. This ultracall allows the Hypervisor to register the partition-
494 scoped and process-scoped page table entries for the Hypervisor
507 ---------
516 .. code-block:: c
536 * Non-volatile registers are restored to their original values.
544 Use cases
552 #. Hypervisor has to use this ultracall to return control to the SVM.
556 --------------------
558 Register an SVM address-range with specified properties.
563 .. code-block:: c
593 Use cases
603 #. When new memory is hot-plugged, a new memory slot gets registered.
607 ----------------------
609 Unregister an SVM address-range that was previously registered using
615 .. code-block:: c
638 Use cases
641 #. Memory hot-remove.
645 ----------------
652 .. code-block:: c
673 Use cases
683 -------------
690 .. code-block:: c
720 Use cases
732 ---------------
739 .. code-block:: c
770 Use cases
777 --------------------
784 .. code-block:: c
807 Use cases
814 ------
821 .. code-block:: c
848 Use cases
881 ----------------
888 .. code-block:: c
909 Use cases
917 ---------------
924 .. code-block:: c
946 Use cases
950 Hypervisor about it. Hypervisor can use this call to finish setting
955 ----------------
962 .. code-block:: c
989 On entry into this hypercall the non-volatile GPRs and FPRs are
997 out pages that were paged-into secure memory, and issue the
1004 Use cases
1011 Hypervisor should use this call to clean up any internal state for
1015 -------------
1022 .. code-block:: c
1025 uint64_t guest_pa, /* guest-physical-address */
1055 Use cases
1065 #. Ultravisor uses this hypercall to page-in a paged-out page. This
1066 can happen when the SVM touches a paged-out page.
1069 inform Ultravisor to do so. Ultravisor will then use this hypercall
1074 ---------------
1081 .. code-block:: c
1084 uint64_t guest_pa, /* guest-physical-address */
1107 Use cases
1117 - `Supporting Protected Computing on IBM Power Architecture <https://developer.ibm.com/articles/l-s…