/linux/kernel/locking/ |
H A D | test-ww_mutex.c | 384 struct stress { struct 425 static void dummy_load(struct stress *stress) in dummy_load() argument 432 struct stress *stress = container_of(work, typeof(*stress), work); in stress_inorder_work() local 433 const int nlocks = stress->nlocks; in stress_inorder_work() 434 struct ww_mutex *locks = stress->locks; in stress_inorder_work() 458 dummy_load(stress); in stress_inorder_work() 467 if (!time_after(jiffies, stress in stress_inorder_work() 385 workstress global() argument 386 locksstress global() argument 387 timeoutstress global() argument 388 nlocksstress global() argument 491 struct stress *stress = container_of(work, typeof(*stress), work); stress_reorder_work() local 550 struct stress *stress = container_of(work, typeof(*stress), work); stress_one_work() local 573 static int stress(int nlocks, int nthreads, unsigned int flags) stress() function 595 struct stress *stress; stress() local [all...] |
/linux/tools/testing/selftests/powerpc/security/ |
H A D | mitigation-patching.sh | 54 if stress-ng > /dev/null 2>&1; then 55 stress="stress-ng" 56 elif stress > /dev/null 2>&1; then 57 stress="stress" 59 stress="" 62 if [[ -n "$stress" ]]; then 63 "$stress" -m "$(nproc)" -t "$TIMEOUT" &
|
/linux/tools/testing/selftests/arm64/fp/ |
H A D | README | 2 standalone stress tests. 13 sve-stress performs an SVE context switch stress test, as described 16 (The fpsimd-stress test works the same way; just substitute "fpsimd" for 25 $ ./sve-stress 64 KVM stress testing 67 To try to reproduce the bugs that we have been observing, sve-stress 88 2) Run the sve-stress on *each* guest with the Vector-Length set to 32: 89 guest$ ./vlset --inherit 32 ./sve-stress 91 3) Run the sve-stress o [all...] |
H A D | Makefile | 10 fp-stress \ 23 TEST_PROGS_EXTENDED := fpsimd-stress sve-stress ssve-stress za-stress
|
/linux/tools/testing/selftests/arm64/gcs/ |
H A D | Makefile | 9 TEST_GEN_PROGS := basic-gcs libc-gcs gcs-locking gcs-stress gcspushm gcsstr 10 TEST_GEN_PROGS_EXTENDED := gcs-stress-thread 23 $(OUTPUT)/gcs-stress-thread: gcs-stress-thread.S
|
H A D | .gitignore | 4 gcs-stress 5 gcs-stress-thread
|
/linux/tools/testing/selftests/prctl/ |
H A D | .gitignore | 2 disable-tsc-ctxt-sw-stress-test 3 disable-tsc-on-off-stress-test
|
H A D | Makefile | 7 TEST_PROGS := disable-tsc-ctxt-sw-stress-test disable-tsc-on-off-stress-test \
|
/linux/Documentation/admin-guide/ |
H A D | workload-tracing.rst | 22 `stress-ng <https://www.mankier.com/1/stress-ng>`_, 67 We used strace to trace the perf, stress-ng, paxtest workloads to illustrate 92 Install stress-ng and paxtest:: 94 apt-get install stress-ng 100 As mentioned earlier, we used strace to trace perf bench, stress-ng and 119 stress-ng is used for performing stress testing on the kernel. It allows 124 to the `stress-ng man-page <https://www.mankier.com/1/stress [all...] |
/linux/drivers/gpu/drm/ci/xfails/ |
H A D | i915-cml-fails.txt | 6 i915_pipe_stress@stress-xrgb8888-untiled,Fail 7 i915_pipe_stress@stress-xrgb8888-ytiled,Fail 8 i915_pm_rpm@gem-execbuf-stress,Timeout 38 kms_pipe_stress@stress-xrgb8888-untiled,Fail 39 kms_pipe_stress@stress-xrgb8888-ytiled,Fail
|
H A D | i915-jsl-fails.txt | 6 i915_pm_rpm@gem-execbuf-stress,Timeout 33 kms_pm_rpm@modeset-stress-extra-wait,Timeout
|
H A D | i915-whl-flakes.txt | 6 kms_pm_rpm@modeset-lpsp-stress
|
H A D | i915-kbl-fails.txt | 5 i915_pm_rpm@gem-execbuf-stress,Timeout
|
H A D | i915-tgl-fails.txt | 9 i915_pm_rpm@gem-execbuf-stress,Timeout
|
H A D | i915-amly-fails.txt | 6 i915_pm_rpm@gem-execbuf-stress,Timeout
|
H A D | i915-apl-fails.txt | 35 kms_pm_rpm@modeset-stress-extra-wait,Timeout
|
H A D | i915-amly-flakes.txt | 48 kms_pm_rpm@modeset-lpsp-stress
|
H A D | i915-whl-fails.txt | 6 i915_pm_rpm@gem-execbuf-stress,Timeout
|
/linux/tools/testing/selftests/mm/ |
H A D | .gitignore | 21 transhuge-stress 30 uffd-stress
|
H A D | Makefile | 90 TEST_GEN_FILES += transhuge-stress 91 TEST_GEN_FILES += uffd-stress 163 $(OUTPUT)/uffd-stress: uffd-common.c
|
H A D | uffd-stress.c | 58 "./uffd-stress anon 100 99999\n\n" 60 "./uffd-stress shmem 1000 99\n\n" 62 "./uffd-stress hugetlb 256 50\n\n" 64 "./uffd-stress hugetlb-private 256 50\n\n" 67 "while ./uffd-stress anon $[RANDOM % 6000 + 10] 999; do true; done\n\n"; 71 fprintf(stderr, "\nUsage: ./uffd-stress <test type> <MiB> <bounces>\n\n"); in usage() 180 static int stress(struct uffd_args *args) in stress() function 331 if (stress(args)) { in userfaultfd_stress()
|
H A D | run_vmtests.sh | 323 uffd_stress_bin=./uffd-stress 327 # uffd-stress expects a region expressed in MiB, so we adjust 497 CATEGORY="thp" run_test ./transhuge-stress -d 20
|
/linux/lib/ |
H A D | Kconfig.kfence | 81 this option is to stress test KFENCE with concurrent error reports 82 and allocations/frees. A value of 0 disables stress testing logic.
|
/linux/drivers/net/ethernet/freescale/fman/ |
H A D | Kconfig | 40 stress with multiple ports injecting line-rate traffic.
|
/linux/tools/memory-model/Documentation/ |
H A D | access-marking.txt | 543 When designing stress tests it is important to ensure that race conditions 573 invoked concurrently, the stress test should force this concurrency to 574 actually happen. KCSAN can evaluate the stress test when the above code 606 If a given stress-test run does not result in KCSAN complaints from 608 stress test needs improvement. If the stress test was to be evaluated 611 false positives when not evaluating the stress test.
|