Lines Matching refs:vector

23 * SVE registers Z0..Z31, P0..P15 and FFR and the current vector length VL, are
26 * The presence of SVE is reported to userspace via HWCAP_SVE in the aux vector
40   be reported in the AT_HWCAP2 aux vector entry.  In addition to this,
77 The size of an SVE vector (Z) register is referred to as the "vector length".
79 To avoid confusion about the units used to express vector length, the kernel
109 * All other SVE state of a thread, including the currently configured vector
110   length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
130   the thread's vector length (in sve_context.vl).
169 * The vector length cannot be changed via signal return.  If sve_context.vl in
170   the signal frame does not match the current vector length, the signal return
177 Some new prctl() calls are added to allow programs to manage the SVE vector
182     Sets the vector length of the calling thread and related flags, where
185     vl is the desired vector length, where sve_vl_valid(vl) must be true.
191 	    Inherit the current vector length across execve().  Otherwise, the
192 	    vector length is reset to the system default at execve().  (See
197 	    Defer the requested vector length change until the next execve()
205 	    This allows launching of a new program with a different vector
214 	EINVAL: SVE not supported, invalid vector length requested, or
220     * Either the calling thread's vector length or the deferred vector length
227     * Any previously outstanding deferred vector length change in the calling
231       PR_SVE_GET_VL.  The vector length reported in this value is the new
232       current vector length for this thread if PR_SVE_SET_VL_ONEXEC was not
233       present in arg; otherwise, the reported vector length is the deferred
234       vector length that will be applied at the next execve() by the calling
237     * Changing the vector length causes all of P0..P15, FFR and all bits of
240       vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
241       flag, does not constitute a change to the vector length for this purpose.
246     Gets the vector length of the calling thread.
255     vector length change (which would only normally be the case between a
258     To extract the vector length from the result, and it with
288 	thread changes its vector length etc.
292 	Target thread's current vector length, in bytes.
296 	Maximum possible vector length for the target thread.
334 * The effects of changing the vector length and/or flags are equivalent to
346   case only the vector length and flags are changed (along with any
353   for the vector length actually set.  The thread's FPSIMD state is
375   to set the default vector length for userspace processes:
380     default vector length to the specified value, unless the value is greater
381     than the maximum vector length supported by the system in which case the
382     default vector length is set to that maximum.
387     At boot, the default vector length is initially set to 64 or the maximum
388     supported vector length, whichever is smaller.  This determines the initial
389     vector length of the init process (PID 1).
391     Reading this file returns the current system default vector length.
393 * At every execve() call, the new vector length of the new process is set to
394   the system default vector length, unless
399     * a deferred vector length change is pending, established via the
402 * Modifying the system default vector length does not affect the vector length
420 * 32 8VL-bit vector registers Z0..Z31
421   For each Zn, Zn bits [127:0] alias the ARMv8-A vector register Vn.
430 * a VL "pseudo-register" that determines the size of each vector register
439 * The maximum vector length is determined by the hardware:
501 * 32 128-bit vector registers V0..V31