| /linux/kernel/locking/ |
| H A D | test-ww_mutex.c | 389 struct stress { struct 431 static void dummy_load(struct stress *stress) in dummy_load() argument 438 struct stress *stress = container_of(work, typeof(*stress), work); in stress_inorder_work() local 439 const int nlocks = stress->nlocks; in stress_inorder_work() 440 struct ww_mutex *locks = stress->locks; in stress_inorder_work() 452 ww_acquire_init(&ctx, stress->class); in stress_inorder_work() 464 dummy_load(stress); in stress_inorder_work() 473 if (!time_after(jiffies, stress->timeout)) { in stress_inorder_work() 485 } while (!time_after(jiffies, stress->timeout)); in stress_inorder_work() 497 struct stress *stress = container_of(work, typeof(*stress), work); in stress_reorder_work() local [all …]
|
| /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/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
|
| /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/tools/testing/selftests/mm/ |
| H A D | .gitignore | 26 transhuge-stress 35 uffd-stress
|
| H A D | Makefile | 92 TEST_GEN_FILES += transhuge-stress 93 TEST_GEN_FILES += uffd-stress 193 $(OUTPUT)/uffd-stress: uffd-common.c
|
| H A D | uffd-stress.c | 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 342 if (stress(args)) { in userfaultfd_stress() 507 "uffd-stress %s\n", argv[1]); in main()
|
| H A D | run_vmtests.sh | 294 uffd_stress_bin=./uffd-stress 444 CATEGORY="thp" run_test ./transhuge-stress -d 20
|
| /linux/tools/testing/selftests/verification/test.d/ |
| H A D | rv_wwnr_printk.tc | 10 stress-ng --cpu-sched "$num" --timer "$num" -t 5 -q
|
| /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/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/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.
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | authors.rst | 69 …and SuSE and Citrix and RedHat testers for finding multiple bugs during excellent stress test runs.
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | mpo-overview.rst | 61 configurations using more than 4 planes. Again, it is important to stress that
|
| /linux/Documentation/core-api/ |
| H A D | pin_user_pages.rst | 66 field, refcount overflows were seen in some huge page stress tests.
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 315 'Page allocation failure. order:0' errors may occur under stress.
|
| H A D | ixgbe.rst | 479 dropped packets during network stress. Bandwidth can be allocated to each of
|
| H A D | ice.rst | 42 Packet drops may occur under receive stress 746 dropped packets during network stress. Bandwidth can be allocated to each of
|
| /linux/Documentation/networking/ |
| H A D | packet_mmap.rst | 1019 you have been warned; generally, this can be useful for stress testing various
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cpusets.rst | 692 than stress the kernel.
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_pstate.rst | 275 it to a lower one unless in a thermal stress or a power limit violation
|