604  * Second page of .data segment is used to test changing PTE permissions.
609  * 2) Change PTE permissions (RW -> RO) of target page within enclave.
612  * 4) Change PTE permissions of target page within enclave back to be RW.
634 	 * have its permissions manipulated.  in TEST_F()
665 	/* Change PTE permissions of target page within the enclave */  in TEST_F()
671 	 * PTE permissions of target page changed to read-only, EPCM  in TEST_F()
672 	 * permissions unchanged (EPCM permissions are RW), attempt to  in TEST_F()
689 	 * Change PTE permissions back to enable enclave to write to the  in TEST_F()
718  * Modifying permissions of TCS page should not be possible.
759 	ioc.permissions = SGX_SECINFO_R;  in TEST_F()
773  * Modify and restore enclave page's EPCM (enclave) permissions from
776  * VMA allows access but EPCM permissions do not.
817 	 * Page that will have its permissions changed is the second data  in TEST_F()
822 	 * VMA permissions of RW.  in TEST_F()
830 	 * any changes to page permissions.  in TEST_F()
862 	 * Change EPCM permissions to read-only. Kernel still considers  in TEST_F()
869 	restrict_ioc.permissions = SGX_SECINFO_R;  in TEST_F()
881 	 * EPCM permissions changed from kernel, need to EACCEPT from enclave.  in TEST_F()
897 	 * EPCM permissions of page is now read-only, expect #PF  in TEST_F()
921 	 * Enter enclave at new TCS to change EPCM permissions to be  in TEST_F()
944 	 * Wrong page permissions that caused original fault has  in TEST_F()
945 	 * now been fixed via EPCM permissions.  in TEST_F()
1011 	 * Kernel will allow new mapping using any permissions if it  in TEST_F()
1141 	 * Kernel will allow new mapping using any permissions if it  in TEST_F()