| /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 on the host with the maximum Vector-Length: 92 host$ ./vlset --inherit --max ./sve-stress [all …]
|
| H A D | Makefile | 10 fp-stress \ 23 TEST_PROGS_EXTENDED := fpsimd-stress sve-stress ssve-stress za-stress
|
| H A D | .gitignore | 3 fp-stress
|
| /linux/tools/testing/selftests/mm/ |
| H A D | test_vmalloc.sh | 62 echo "Run stability tests. In order to stress vmalloc subsystem all" 75 echo "for deep performance analysis as well as stress testing." 84 echo -n "Usage: $0 [ performance ] | [ stress ] | | [ smoke ] | " 111 echo "# Stress testing" 112 echo "./${DRIVER}.sh stress" 164 elif [[ "$1" = "stress" ]]; then
|
| H A D | uffd-stress.c | 3 * Stress userfaultfd syscall. 64 "./uffd-stress anon 100 99999\n\n" 66 "./uffd-stress shmem 1000 99\n\n" 68 "./uffd-stress hugetlb 256 50\n\n" 70 "./uffd-stress hugetlb-private 256 50\n\n" 73 "while ./uffd-stress anon $[RANDOM % 6000 + 10] 999; do true; done\n\n"; 77 fprintf(stderr, "\nUsage: ./uffd-stress <test type> <MiB> <bounces>\n\n"); in usage() 193 static int stress(struct uffd_args *args) in stress() function 348 if (stress(args)) { in userfaultfd_stress()
|
| H A D | .gitignore | 21 transhuge-stress 30 uffd-stress
|
| H A D | Makefile | 92 TEST_GEN_FILES += transhuge-stress 93 TEST_GEN_FILES += uffd-stress 166 $(OUTPUT)/uffd-stress: uffd-common.c
|
| H A D | run_vmtests.sh | 328 uffd_stress_bin=./uffd-stress 332 # of (nr_parallel - 1) is done (see nr_parallel in uffd-stress.c) to have some 335 # uffd-stress expects a region expressed in MiB, so we adjust 506 CATEGORY="thp" run_test ./transhuge-stress -d 20
|
| /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 | gcs-stress.c | 116 ret = execl("gcs-stress-thread", "gcs-stress-thread", NULL); in start_thread() 117 fprintf(stderr, "execl(gcs-stress-thread) failed: %d (%s)\n", in start_thread()
|
| /linux/tools/testing/selftests/sync/ |
| H A D | synctest.h | 58 /* Stress test - parallelism */ 61 /* Stress test - consumer */ 64 /* Stress test - merging */
|
| /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/lib/ |
| H A D | Kconfig.kfence | 76 int "Stress testing of fault handling and error reporting" if EXPERT 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/tools/testing/selftests/ublk/ |
| H A D | test_stress_01.sh | 22 _prep_test "stress" "run IO and remove device" 33 _cleanup_test "stress"
|
| H A D | test_stress_02.sh | 22 _prep_test "stress" "run IO and kill ublk server" 35 _cleanup_test "stress"
|
| H A D | test_stress_04.sh | 25 _prep_test "stress" "run IO and kill ublk server(zero copy)" 50 _cleanup_test "stress"
|
| H A D | test_stress_03.sh | 26 _prep_test "stress" "run IO and remove device(zero copy)" 53 _cleanup_test "stress"
|
| H A D | test_stress_05.sh | 48 _prep_test "stress" "run IO and remove device with recovery enabled" 83 _cleanup_test "stress"
|
| /linux/tools/memory-model/Documentation/ |
| H A D | access-marking.txt | 540 Checking Stress-Test Race Coverage 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.
|
| /linux/tools/testing/selftests/cgroup/ |
| H A D | with_stress.sh | 61 echo "Usage $0 [ -s stress ] ... [ -d duration ] [-c controller] cmd args .." 69 echo "Unknown stress $OPTARG"
|
| /linux/Documentation/locking/ |
| H A D | locktorture.rst | 34 Number of kernel threads that will stress exclusive lock 39 Number of kernel threads that will stress shared lock
|
| /linux/tools/testing/selftests/futex/ |
| H A D | run.sh | 9 # Run all tests under the functional, performance, and stress directories.
|
| /linux/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 40 stress with multiple ports injecting line-rate traffic.
|
| /linux/tools/perf/bench/ |
| H A D | futex-hash.c | 5 * futex-hash: Stress the hell out of the Linux kernel futex uaddr hashing. 90 * We want the futex calls to fail in order to stress in workerfn()
|