Home
last modified time | relevance | path

Searched refs:TIF_SVE (Results 1 - 14 of 14) sorted by relevance

/kernel/linux/linux-5.10/arch/arm64/kernel/
H A Dfpsimd.c224 WARN_ON(test_tsk_thread_flag(task, TIF_SVE)); in sve_free()
230 * TIF_SVE controls whether a task can use SVE without trapping while
239 * * TIF_SVE set:
252 * During any syscall, the kernel may optionally clear TIF_SVE and
255 * * TIF_SVE clear:
259 * sets TIF_SVE.
272 * irrespective of whether TIF_SVE is clear or set, since these are
288 if (system_supports_sve() && test_thread_flag(TIF_SVE)) in task_fpsimd_load()
310 if (system_supports_sve() && test_thread_flag(TIF_SVE)) { in fpsimd_save()
539 if (!test_tsk_thread_flag(task, TIF_SVE)) in fpsimd_sync_to_sve()
[all...]
H A Dsignal.c209 clear_thread_flag(TIF_SVE); in restore_fpsimd_context()
233 if (test_thread_flag(TIF_SVE)) in preserve_sve_context()
273 clear_thread_flag(TIF_SVE); in restore_sve_fpsimd_context()
300 set_thread_flag(TIF_SVE); in restore_sve_fpsimd_context()
593 if (add_all || test_thread_flag(TIF_SVE)) { in setup_sigframe_layout()
H A Dsyscall.c179 clear_thread_flag(TIF_SVE); in sve_user_discard()
H A Dprocess.c367 * For consistency, also clear TIF_SVE here: this could be done in arch_dup_task_struct()
369 * maintainers it is best not to leave TIF_SVE and sve_state in in arch_dup_task_struct()
373 clear_tsk_thread_flag(dst, TIF_SVE); in arch_dup_task_struct()
H A Dptrace.c725 header->flags = test_tsk_thread_flag(target, TIF_SVE) ? in sve_init_header_from_task()
833 clear_tsk_thread_flag(target, TIF_SVE); in sve_set()
857 set_tsk_thread_flag(target, TIF_SVE); in sve_set()
/kernel/linux/linux-5.10/arch/arm64/kvm/
H A Dfpsimd.c58 * TIF_SVE is backed up here, since it may get clobbered with guest state.
70 if (test_thread_flag(TIF_SVE)) in kvm_arch_vcpu_load_fp()
93 update_thread_flag(TIF_SVE, vcpu_has_sve(vcpu)); in kvm_arch_vcpu_ctxsync_fp()
130 update_thread_flag(TIF_SVE, in kvm_arch_vcpu_put_fp()
/kernel/linux/linux-6.6/arch/arm64/kernel/
H A Dfpsimd.c311 * TIF_SVE controls whether a task can use SVE without trapping while
320 * * TIF_SVE or SVCR.SM set:
325 * During any syscall, the kernel may optionally clear TIF_SVE and
328 * * TIF_SVE clear:
332 * sets TIF_SVE.
334 * During any syscall, the kernel may optionally clear TIF_SVE and
369 * irrespective of whether TIF_SVE is clear or set, since these are
392 if (test_and_clear_thread_flag(TIF_SVE)) in task_fpsimd_load()
397 !WARN_ON_ONCE(!test_and_set_thread_flag(TIF_SVE))) in task_fpsimd_load()
400 if (test_thread_flag(TIF_SVE)) in task_fpsimd_load()
[all...]
H A Dsmccc-call.S26 tbnz x16, #TIF_SVE, 2f // Does that state include SVE?
H A Dsignal.c220 clear_thread_flag(TIF_SVE); in restore_fpsimd_context()
309 clear_thread_flag(TIF_SVE); in restore_sve_fpsimd_context()
332 clear_thread_flag(TIF_SVE); in restore_sve_fpsimd_context()
346 set_thread_flag(TIF_SVE); in restore_sve_fpsimd_context()
H A Dptrace.c747 fpsimd_only = !test_tsk_thread_flag(target, TIF_SVE); in sve_init_header_from_task()
912 clear_tsk_thread_flag(target, TIF_SVE); in sve_set_common()
935 clear_tsk_thread_flag(target, TIF_SVE); in sve_set_common()
949 set_tsk_thread_flag(target, TIF_SVE); in sve_set_common()
H A Dprocess.c300 * For consistency, also clear TIF_SVE here: this could be done in arch_dup_task_struct()
306 clear_tsk_thread_flag(dst, TIF_SVE); in arch_dup_task_struct()
H A Dentry-common.c379 if (test_thread_flag(TIF_SVE)) { in fp_user_discard()
/kernel/linux/linux-5.10/arch/arm64/include/asm/
H A Dthread_info.h82 #define TIF_SVE 23 /* Scalable Vector Extension in use */ macro
100 #define _TIF_SVE (1 << TIF_SVE)
/kernel/linux/linux-6.6/arch/arm64/include/asm/
H A Dthread_info.h77 #define TIF_SVE 23 /* Scalable Vector Extension in use */ macro
96 #define _TIF_SVE (1 << TIF_SVE)

Completed in 16 milliseconds