Lines Matching full:shared

98 There are essentially two classes of TDX memory: private and shared.
100 against access from the hypervisor.  Shared memory is expected to be
101 shared between guest and hypervisor and does not receive full TDX
105 private or shared.  It selects the behavior with a bit in its page table
107 information in shared memory, exposing it to the untrusted hypervisor.
109 #VE on Shared Memory
112 Access to shared mappings can cause a #VE.  The hypervisor ultimately
113 controls whether a shared memory access causes a #VE, so the guest must be
114 careful to only reference shared pages it can safely handle a #VE.  For
115 instance, the guest should be careful not to access shared memory in the
118 Shared mapping content is entirely controlled by the hypervisor. The guest
119 should only use shared mappings for communicating with the hypervisor.
120 Shared mappings must never be used for sensitive memory content like kernel
121 stacks.  A good rule of thumb is that hypervisor-shared memory should be
125 MMIO for virtual devices is implemented as shared memory.  The guest must
191 Shared Memory Conversions
197 memory must be converted between shared and private.  This can be
200  * set_memory_decrypted() converts a range of pages to shared.
203 Device drivers are the primary user of shared memory, but there's no need
208 converted to shared on boot.