Lines Matching +full:machine +full:- +full:mode
1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
19 When enabled, PEF adds a new higher privileged mode, called Ultravisor
20 mode, to POWER architecture. Along with the new mode there is new
22 for short). Ultravisor mode is the highest privileged mode in POWER
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
39 executed by an authorized machine. All virtual machines utilize
56 process is running in secure mode, MSR(S) bit 41. MSR(S)=1, process
57 is in secure mode, MSR(s)=0 process is in normal mode.
73 **Secure Mode MSR Settings**
75 +---+---+---+---------------+
79 +---+---+---+---------------+
81 +---+---+---+---------------+
83 +---+---+---+---------------+
85 +---+---+---+---------------+
87 **Normal Mode MSR Settings**
89 +---+---+---+---------------+
93 +---+---+---+---------------+
95 +---+---+---+---------------+
97 +---+---+---+---------------+
99 +---+---+---+---------------+
102 that are running in secure mode can access secure memory.
117 * When a process is running in secure mode all hypercalls
120 * When a process is in secure mode all interrupts go to the
131 If SMFCTRL(D) is not set they do not work in secure mode. When set,
139 * LDBAR (LD Base Address Register) and IMC (In-Memory Collection)
140 non-architected registers. An attempt to write to them will cause a
156 (Enter Secure Mode), to make the transition.
161 passes control in secure mode.
180 is a mode of AES that provides integrity and secrecy concurrently.
183 with the Ultravisor by a new HMM plug-in in the Hypervisor.
209 * SVM: Secure Virtual Machine.
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-
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,
389 #. When a normal VM switches to secure mode, all its pages residing
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 */
441 because it is paged-out to disk, Ultravisor needs to know that the
446 -------------
454 .. code-block:: c
473 of a secure virtual machine or if called from a
479 Validate and write a LPID and its partition-table-entry for the given
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.
556 --------------------
558 Register an SVM address-range with specified properties.
563 .. code-block:: c
597 #. When a virtual machine goes secure, all the memory slots managed by
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
641 #. Memory hot-remove.
645 ----------------
652 .. code-block:: c
683 -------------
690 .. code-block:: c
732 ---------------
739 .. code-block:: c
777 --------------------
784 .. code-block:: c
814 ------
816 Secure the virtual machine (*enter secure mode*).
821 .. code-block:: c
844 Secure the virtual machine. On successful completion, return
845 control to the virtual machine at the address specified in the
851 #. A normal virtual machine can choose to switch to a secure mode.
881 ----------------
883 Begin the process of converting a normal virtual machine into an SVM.
888 .. code-block:: c
903 Initiate the process of securing a virtual machine. This involves
913 has initiated the process of switching to secure mode.
917 ---------------
924 .. code-block:: c
943 Complete the process of securing a virtual machine. This call must
949 On successfully securing a virtual machine, the Ultravisor informs
951 up its internal state for this virtual machine.
955 ----------------
962 .. code-block:: c
985 Abort the process of securing a virtual machine. This call must
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
1008 encounters an error while securing a virtual machine, either due
1012 this virtual machine and return to the VM.
1015 -------------
1022 .. code-block:: c
1025 uint64_t guest_pa, /* guest-physical-address */
1065 #. Ultravisor uses this hypercall to page-in a paged-out page. This
1066 can happen when the SVM touches a paged-out page.
1074 ---------------
1081 .. code-block:: c
1084 uint64_t guest_pa, /* guest-physical-address */
1117 - `Supporting Protected Computing on IBM Power Architecture <https://developer.ibm.com/articles/l-s…