Lines Matching refs:normal
57 is in secure mode, MSR(s)=0 process is in normal mode.
101 * Memory is partitioned into secure and normal memory. Only processes
152 * SVMs are created from normal VM using (open source) tooling supplied
155 * All SVMs start as normal VMs and utilize an ultracall, UV_ESM
182 * The movement of data between normal and secure pages is coordinated
196 * Normal page: Page backed by normal memory and available to
199 * Shared page: A page backed by normal memory and available to both
242 to normal memory may be encrypted using dynamically generated keys.
269 Encrypt and move the contents of a page from secure memory to normal
302 Hypervisor in a normal page.
324 then allocate a normal page and issue the ``UV_PAGE_OUT`` ultracall
326 page into the normal page.
330 which the Hypervisor can access. The data in the normal page will
336 Move the contents of a page from normal memory to secure memory.
367 Move the contents of the page identified by ``src_ra`` from normal
389 #. When a normal VM switches to secure mode, all its pages residing
390 in normal memory, are moved into secure memory.
489 virtual machines (both secure and normal). The Hypervisor
491 reside in normal memory.
502 the PATE entries for a normal VM and can change the PATE entry
851 #. A normal virtual machine can choose to switch to a secure mode.
883 Begin the process of converting a normal virtual machine into an SVM.
906 pages from normal to secure memory etc. When the process is
980 normal VM).
1017 Move the contents of a page from normal memory to secure memory.
1058 #. When a normal VM becomes a secure VM (using the UV_ESM ultracall),
1060 the VM from normal memory to secure memory.
1063 in normal memory that can be shared between the SVM and Hypervisor.
1070 and inform Hypervisor that it has released access to the normal
1076 Move the contents of the page to normal memory.
1101 Move the contents of the page identified by ``guest_pa`` to normal
1111 contents of some secure pages, into normal pages using this