Lines Matching full:be

9 intended to be exhaustive.
28   GCSPR_EL0.  This is readable by userspace but can only be updated
43   at runtime this should be done with great care.
47 * GCS specific errors (those reported with EC 0x2d) will be reported as
56   in LR match those in the GCS, the LR will be ignored.  This is not supported
66   should be used.
82   status of the specified GCS mode bits will be rejected.
84 * PR_LOCK_SHADOW_STACK_STATUS allows any bit to be locked, this allows
91   thread that called them, any other running threads will be unaffected.
97 * The current GCS configuration for a thread may be read with the
103   any attempt to reenable GCS for the thread will be rejected, this may be
106 * It should be noted that since enabling GCS will result in GCS becoming
109   usage will be that GCS is enabled very early in execution of a program.
116 * When GCS is enabled for a thread a new Guarded Control Stack will be
121   new Guarded Control Stack will be allocated for the new thread with
125   the top 8 bytes of the stack will be initialised to 0 and GCSPR_EL0 will
126   be set to point to the address of this 0 value, this can be used to
129 * Additional Guarded Control Stacks can be allocated using the
134   SHADOW_STACK_SET_TOKEN is specified a cap will be placed on the stack,
135   if SHADOW_STACK_SET_MARKER is not specified the cap will be the top 8
136   bytes of the stack and if it is specified then the cap will be the next
141   multiple of 8 bytes larger than 8 bytes and must be 8 bytes aligned.
143 * An address can be specified to map_shadow_stack(), if one is provided then
144   it must be aligned to a page boundary.
147   that thread will be freed.  Note carefully that if the stack has been
148   switched this may not be the stack currently in use by the thread.
156   be present on systems that support GCS.
165   GCS cap token will be written to the GCS, this is an architectural GCS cap
172   return handler will be pushed onto the GCS, allowing return from the signal
173   handler via RET as normal.  This will not be reported in the gcs_context in
183   and GCSPR_EL0 will be restored from that context prior to further
187   configuration will be unchanged.
190   point to a valid GCS signal cap record, this will be popped from the
194   attempt to change the GCS configuration will be treated as an error.  This
197 * GCS may be disabled via signal return but any attempt to enable GCS via
198   signal return will be rejected.
207 * The GCS mode, including enable and disable, may be configured via ptrace.
208   If GCS is enabled via ptrace no new GCS will be allocated for the thread.
216 * NT_ARM_GCS notes will be added to each coredump for each thread of the
217   dumped process.  The contents will be equivalent to the data that would