Changes in avx.c

bbfd5594756011167b8f8de9a00e0c946afda1e6 - Merge drm/drm-next into drm-intel-gt-next

Wed, 28 May 2025 09:20:17 +0200

Merge drm/drm-next into drm-intel-gt-nextNeed to pull in a67221b5eb8d ("drm/i915/dp: Return min bpc supported by source instead of 0")in order to fix build breakage on GCC 9.4.0 (from Ubuntu 20.04).Signed-off-by: Joonas Lahtinen List of files: /linux/tools/testing/selftests/x86/avx.c

db5302ae571beec635c1a96e7f72926a4e65195e - Merge drm/drm-next into drm-intel-next

Fri, 16 May 2025 09:22:36 +0200

Merge drm/drm-next into drm-intel-nextBackmerge to sync with v6.15-rc, xe, and specifically async flip changesin drm-misc.Signed-off-by: Jani Nikula List of files: /linux/tools/testing/selftests/x86/avx.c

4f9786035f9e519db41375818e1d0b5f20da2f10 - Merge branch 'next' into for-linus

Mon, 02 Jun 2025 06:41:07 +0200

Merge branch 'next' into for-linusPrepare input updates for 6.16 merge window. List of files: /linux/tools/testing/selftests/x86/avx.c

d51b9d81f7883f526b26e3ab903e646274aebeb1 - Merge tag 'v6.15-rc6' into next

Fri, 16 May 2025 01:20:39 +0200

Merge tag 'v6.15-rc6' into nextSync up with mainline to bring in xpad controller changes. List of files: /linux/tools/testing/selftests/x86/avx.c

844e31bbaef7c8a6ff2c0fbac45c0c85b5484482 - Merge remote-tracking branch 'drm-misc/drm-misc-next' into msm-next

Tue, 29 Apr 2025 22:42:29 +0200

Merge remote-tracking branch 'drm-misc/drm-misc-next' into msm-nextMerge drm-misc-next to get commit Fixes: fec450ca15af ("drm/display:hdmi: provide central data authority for ACR params").Signed-off-by: Rob Clark List of files: /linux/tools/testing/selftests/x86/avx.c

3ab7ae8e07f888f223027f0ef84d33e43919ad55 - Merge drm/drm-next into drm-xe-next

Thu, 24 Apr 2025 13:34:55 +0200

Merge drm/drm-next into drm-xe-nextBackmerge to bring in linux 6.15-rc.Signed-off-by: Thomas Hellström List of files: /linux/tools/testing/selftests/x86/avx.c

1afba39f9305fe4061a4e70baa6ebab9d41459da - Merge drm/drm-next into drm-misc-next

Mon, 07 Apr 2025 13:47:40 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get v6.15-rc1 into drm-misc-next. Also fixes abuild issue when enabling CONFIG_DRM_SCHED_KUNIT_TEST.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/x86/avx.c

1260ed77798502de9c98020040d2995008de10cc - Merge drm/drm-fixes into drm-misc-fixes

Tue, 08 Apr 2025 10:15:47 +0200

Merge drm/drm-fixes into drm-misc-fixesBackmerging to get updates from v6.15-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/tools/testing/selftests/x86/avx.c

2487b6b9bf2874cfca7efb59c95650c5b1d88d43 - Merge branch 'linus' into x86/urgent, to pick up fixes and refresh the branch

Tue, 25 Mar 2025 08:17:25 +0100

Merge branch 'linus' into x86/urgent, to pick up fixes and refresh the branchSigned-off-by: Ingo Molnar List of files: /linux/tools/testing/selftests/x86/avx.c

71b639af06ef1c422df87be36ad411bc31abf1ce - Merge tag 'x86-fpu-2025-03-22' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Tue, 25 Mar 2025 06:27:18 +0100

Merge tag 'x86-fpu-2025-03-22' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull x86/fpu updates from Ingo Molnar: - Improve crypto performance by making kernel-mode FPU reliably usable in softirqs ((Eric Biggers) - Fully optimize out WARN_ON_FPU() (Eric Biggers) - Initial steps to support Support Intel APX (Advanced Performance Extensions) (Chang S. Bae) - Fix KASAN for arch_dup_task_struct() (Benjamin Berg) - Refine and simplify the FPU magic number check during signal return (Chang S. Bae) - Fix inconsistencies in guest FPU xfeatures (Chao Gao, Stanislav Spassov) - selftests/x86/xstate: Introduce common code for testing extended states (Chang S. Bae) - Misc fixes and cleanups (Borislav Petkov, Colin Ian King, Uros Bizjak)* tag 'x86-fpu-2025-03-22' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/fpu/xstate: Fix inconsistencies in guest FPU xfeatures x86/fpu: Clarify the "xa" symbolic name used in the XSTATE* macros x86/fpu: Use XSAVE{,OPT,C,S} and XRSTOR{,S} mnemonics in xstate.h x86/fpu: Improve crypto performance by making kernel-mode FPU reliably usable in softirqs x86/fpu/xstate: Simplify print_xstate_features() x86/fpu: Refine and simplify the magic number check during signal return selftests/x86/xstate: Fix spelling mistake "hader" -> "header" x86/fpu: Avoid copying dynamic FP state from init_task in arch_dup_task_struct() vmlinux.lds.h: Remove entry to place init_task onto init_stack selftests/x86/avx: Add AVX tests selftests/x86/xstate: Clarify supported xstates selftests/x86/xstate: Consolidate test invocations into a single entry selftests/x86/xstate: Introduce signal ABI test selftests/x86/xstate: Refactor ptrace ABI test selftests/x86/xstate: Refactor context switching test selftests/x86/xstate: Enumerate and name xstate components selftests/x86/xstate: Refactor XSAVE helpers for general use selftests/x86: Consolidate redundant signal helper functions x86/fpu: Fix guest FPU state buffer allocation size x86/fpu: Fully optimize out WARN_ON_FPU() List of files: /linux/tools/testing/selftests/x86/avx.c

bfc98dbcb3c75c6e2eb1dcf389d02a8c2419c41c - selftests/x86/avx: Add AVX tests

Wed, 26 Feb 2025 02:07:29 +0100

selftests/x86/avx: Add AVX testsAdd xstate testing specifically for those vector register states,validating kernel's context switching and ensuring ABI compliance.Use the established xstate testing framework.Alternatively, this invocation could be placed directly inxstate.c::main(). However, the current test file naming convention, whichclearly specifies the tested area, seems reasonable. Adding avx.cconsiderably aligns with that convention.The test output should be like this for ZMM_Hi256 as an example: $ avx_64 ... [RUN] AVX-512 ZMM_Hi256: check context switches, 10 iterations, 5 threads. [OK] No incorrect case was found. [RUN] AVX-512 ZMM_Hi256: inject xstate via ptrace(). [OK] 'xfeatures' in SW reserved area was correctly written [OK] xstate was correctly updated. [RUN] AVX-512 ZMM_Hi256: load xstate and raise SIGUSR1 [OK] 'magic1' is valid [OK] 'xfeatures' in SW reserved area is valid [OK] 'xfeatures' in XSAVE header is valid [OK] xstate delivery was successful [OK] 'magic2' is valid [RUN] AVX-512 ZMM_Hi256: load new xstate from sighandler and check it after sigreturn [OK] xstate was restored correctlyBut systems without AVX-512 will look like: ... The kernel does not support feature number: 5 The kernel does not support feature number: 6 The kernel does not support feature number: 7Signed-off-by: Chang S. Bae Signed-off-by: Ingo Molnar Link: https://lore.kernel.org/r/20250226010731.2456-10-chang.seok.bae@intel.com List of files: /linux/tools/testing/selftests/x86/avx.c