Lines Matching full:encryption

4 AMD Memory Encryption
7 Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV) are
23 A page is encrypted when a page table entry has the encryption bit set (see
24 below on how to determine its position).  The encryption bit can also be
26 successive level of page tables can also be encrypted by setting the encryption
29 encryption bit is set in cr3, doesn't imply the full hierarchy is encrypted.
30 Each page table entry in the hierarchy needs to have the encryption bit set to
31 achieve that. So, theoretically, you could have the encryption bit set in cr3
32 so that the PGD is encrypted, but not set the encryption bit in the PGD entry
38 memory. Since the memory encryption bit is controlled by the guest OS when it
40 forces the memory encryption bit to 1.
50 			   encryption
52 			   memory encryption is enabled (this only affects
57 determine if SME is enabled and/or to enable memory encryption::
60 		Bit[23]   0 = memory encryption features are disabled
61 			  1 = memory encryption features are enabled
67 		Bit[0]	  0 = memory encryption is not active
68 			  1 = memory encryption is active
71 in the physical address space as a result of enabling memory encryption (see
74 Linux itself will not set it and memory encryption will not be possible.
86 	  the encryption bit to page table entries (the SME mask in the
91 will not be necessary to activate the Linux memory encryption support.
94 then memory encryption can be enabled by supplying mem_encrypt=on on the
96 will not be able to activate memory encryption, even if configured to do