Home
last modified time | relevance | path

Searched refs:stress (Results 1 – 25 of 32) sorted by relevance

12

/linux/kernel/locking/
H A Dtest-ww_mutex.c389 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 DREADME2 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 DMakefile10 fp-stress \
23 TEST_PROGS_EXTENDED := fpsimd-stress sve-stress ssve-stress za-stress
H A D.gitignore3 fp-stress
/linux/tools/testing/selftests/arm64/gcs/
H A DMakefile9 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.gitignore2 disable-tsc-ctxt-sw-stress-test
3 disable-tsc-on-off-stress-test
H A DMakefile7 TEST_PROGS := disable-tsc-ctxt-sw-stress-test disable-tsc-on-off-stress-test \
/linux/tools/testing/selftests/mm/
H A DMakefile91 TEST_GEN_FILES += transhuge-stress
92 TEST_GEN_FILES += uffd-stress
193 $(OUTPUT)/uffd-stress: uffd-common.c
H A Duffd-stress.c64 "./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 Drun_vmtests.sh293 uffd_stress_bin=./uffd-stress
445 CATEGORY="thp" run_test ./transhuge-stress -d 20
/linux/tools/testing/selftests/verification/test.d/
H A Drv_wwnr_printk.tc4 # requires: available_reactors wwnr:monitor printk:reactor stress-ng:program
10 stress-ng --cpu-sched "$num" --timer "$num" -t 5 -q &
/linux/lib/
H A DKconfig.kfence81 this option is to stress test KFENCE with concurrent error reports
82 and allocations/frees. A value of 0 disables stress testing logic.
H A DKconfig.debug2597 tristate "Test module for stress/performance analysis of vmalloc allocator"
2602 stress and performance analysis. So, any new change for vmalloc
2609 tristate "Test module for stress/performance analysis of workqueue"
3151 tristate "kmod stress tester"
3161 it stress tests request_module() and this will very likely cause
3187 This allows us to stress test find_symbol() through the kallsyms
3198 We stress test find_symbol() through two means:
3228 stress test find_symbol() with thousands of symbols. At the same
3230 symbols, and if BTF is enabled this also stress tests adding BTF
3386 tristate "Test module for correctness and stress o
[all...]
/linux/tools/memory-model/Documentation/
H A Daccess-marking.txt543 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/drivers/net/ethernet/freescale/fman/
H A DKconfig40 stress with multiple ports injecting line-rate traffic.
/linux/Documentation/locking/
H A Dlocktorture.rst34 Number of kernel threads that will stress exclusive lock
39 Number of kernel threads that will stress shared lock
/linux/Documentation/admin-guide/cifs/
H A Dauthors.rst69 …and SuSE and Citrix and RedHat testers for finding multiple bugs during excellent stress test runs.
/linux/Documentation/core-api/real-time/
H A Dkernel-configuration.rst128 thorough stress testing using tools like ``glmark2`` while measuring the
/linux/Documentation/gpu/amdgpu/display/
H A Dmpo-overview.rst61 configurations using more than 4 planes. Again, it is important to stress that
/linux/Documentation/core-api/
H A Dpin_user_pages.rst66 field, refcount overflows were seen in some huge page stress tests.
/linux/kernel/trace/
H A DKconfig1018 tristate "Ring buffer benchmark stress tester"
1021 This option creates a test to stress the ring buffer and benchmark it.
1183 to the ring buffer, to test/stress the nesting ability.
/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Diavf.rst315 'Page allocation failure. order:0' errors may occur under stress.
H A Dixgbe.rst479 dropped packets during network stress. Bandwidth can be allocated to each of
H A Dice.rst42 Packet drops may occur under receive stress
746 dropped packets during network stress. Bandwidth can be allocated to each of
/linux/kernel/rcu/
H A DKconfig191 systems, but if you are stress-testing the RCU implementation

12