| /Linux-v5.10/kernel/locking/ |
| D | test-ww_mutex.c | 342 struct stress { struct
373 static void dummy_load(struct stress *stress) in dummy_load() argument
380 struct stress *stress = container_of(work, typeof(*stress), work); in stress_inorder_work() local
381 const int nlocks = stress->nlocks; in stress_inorder_work()
382 struct ww_mutex *locks = stress->locks; in stress_inorder_work()
406 dummy_load(stress); in stress_inorder_work()
426 } while (!time_after(jiffies, stress->timeout)); in stress_inorder_work()
429 kfree(stress); in stress_inorder_work()
439 struct stress *stress = container_of(work, typeof(*stress), work); in stress_reorder_work() local
446 order = get_random_order(stress->nlocks); in stress_reorder_work()
[all …]
|
| /Linux-v5.10/tools/testing/selftests/arm64/fp/ |
| 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 …]
|
| D | Makefile | 5 TEST_PROGS_EXTENDED := fpsimd-test fpsimd-stress sve-test sve-stress vlset
|
| /Linux-v5.10/tools/testing/selftests/prctl/ |
| D | .gitignore | 2 disable-tsc-ctxt-sw-stress-test
3 disable-tsc-on-off-stress-test
|
| D | Makefile | 7 TEST_PROGS := disable-tsc-ctxt-sw-stress-test disable-tsc-on-off-stress-test \
|
| /Linux-v5.10/tools/testing/selftests/vm/ |
| D | .gitignore | 12 transhuge-stress
|
| D | Makefile | 38 TEST_GEN_FILES += transhuge-stress
|
| D | userfaultfd.c | 708 static int stress(struct uffd_stats *uffd_stats) in stress() function
1370 if (stress(uffd_stats)) in userfaultfd_stress()
|
| /Linux-v5.10/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 39 stress with multiple ports injecting line-rate traffic.
|
| /Linux-v5.10/Documentation/locking/ |
| D | locktorture.rst | 34 Number of kernel threads that will stress exclusive lock
39 Number of kernel threads that will stress shared lock
|
| /Linux-v5.10/Documentation/admin-guide/cifs/ |
| D | authors.rst | 69 …and SuSE and Citrix and RedHat testers for finding multiple bugs during excellent stress test runs.
|
| /Linux-v5.10/Documentation/vm/ |
| D | hwpoison.rst | 155 value). This allows stress testing of many kinds of
|
| /Linux-v5.10/Documentation/power/regulator/ |
| D | consumer.rst | 180 consumers under regulator stress or failure conditions.
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | ixgb.rst | 445 Under small packets UDP stress test with 10GbE driver, the Linux system
452 Under stress conditions, if TX hangs occur, turning off TSO
|
| D | iavf.rst | 315 'Page allocation failure. order:0' errors may occur under stress.
|
| D | ixgbe.rst | 463 dropped packets during network stress. Bandwidth can be allocated to each of
|
| /Linux-v5.10/kernel/trace/ |
| D | Kconfig | 687 tristate "Ring buffer benchmark stress tester"
690 This option creates a test to stress the ring buffer and benchmark it.
786 to the ring buffer, to test/stress the nesting ability.
|
| /Linux-v5.10/kernel/rcu/ |
| D | Kconfig | 129 systems, but if you are stress-testing the RCU implementation
|
| /Linux-v5.10/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 272 2. If a regular CPU hotplug stress test happens to race with the freezer due
|
| /Linux-v5.10/drivers/usb/misc/ |
| D | Kconfig | 187 with specialized device firmware for regression and stress testing,
|
| /Linux-v5.10/Documentation/core-api/ |
| D | pin_user_pages.rst | 67 page overflows were seen in some huge page stress tests.
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | intel-speed-select.rst | 222 #stress -c 64
786 MHz can be achieved. If there is some busy workload on cpu 0 - 11 (e.g. stress)
|
| /Linux-v5.10/net/ |
| D | Kconfig | 343 stress testing and performance analysis. If you don't understand
|
| /Linux-v5.10/lib/ |
| D | Kconfig.debug | 2137 tristate "Test module for stress/performance analysis of vmalloc allocator"
2143 stress and performance analysis. So, any new change for vmalloc
2300 tristate "kmod stress tester"
2315 it stress tests request_module() and this will very likely cause
|
| /Linux-v5.10/arch/ |
| D | Kconfig | 99 This technique lowers overhead and stress on the branch prediction
|
