Lines Matching refs:encryption

17 A page is encrypted when a page table entry has the encryption bit set (see
18 below on how to determine its position).  The encryption bit can also be
20 successive level of page tables can also be encrypted by setting the encryption
23 encryption bit is set in cr3, doesn't imply the full hierarchy is encrypted.
24 Each page table entry in the hierarchy needs to have the encryption bit set to
25 achieve that. So, theoretically, you could have the encryption bit set in cr3
26 so that the PGD is encrypted, but not set the encryption bit in the PGD entry
32 memory. Since the memory encryption bit is controlled by the guest OS when it
34 forces the memory encryption bit to 1.
44 			   encryption
46 			   memory encryption is enabled (this only affects
51 determine if SME is enabled and/or to enable memory encryption:
54 		Bit[23]   0 = memory encryption features are disabled
55 			  1 = memory encryption features are enabled
61 		Bit[0]	  0 = memory encryption is not active
62 			  1 = memory encryption is active
65 in the physical address space as a result of enabling memory encryption (see
68 Linux itself will not set it and memory encryption will not be possible.
79 	  the encryption bit to page table entries (the SME mask in the
84 not be necessary to activate the Linux memory encryption support.  If the BIOS
86 memory encryption by default (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y) or
88 not enable SME, then Linux will not be able to activate memory encryption, even