| /Linux-v6.6/kernel/locking/ |
| D | test-ww_mutex.c | 382 struct stress { struct
413 static void dummy_load(struct stress *stress) in dummy_load() argument
420 struct stress *stress = container_of(work, typeof(*stress), work); in stress_inorder_work() local
421 const int nlocks = stress->nlocks; in stress_inorder_work()
422 struct ww_mutex *locks = stress->locks; in stress_inorder_work()
446 dummy_load(stress); in stress_inorder_work()
466 } while (!time_after(jiffies, stress->timeout)); in stress_inorder_work()
469 kfree(stress); in stress_inorder_work()
479 struct stress *stress = container_of(work, typeof(*stress), work); in stress_reorder_work() local
486 order = get_random_order(stress->nlocks); in stress_reorder_work()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/powerpc/security/ |
| D | mitigation-patching.sh | 55 if stress-ng > /dev/null 2>&1; then
56 stress="stress-ng"
57 elif stress > /dev/null 2>&1; then
58 stress="stress"
60 stress=""
63 if [[ -n "$stress" ]]; then
64 "$stress" -m "$(nproc)" -t "$TIMEOUT" &
|
| /Linux-v6.6/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 | 8 TEST_GEN_PROGS := fp-stress \
20 TEST_PROGS_EXTENDED := fpsimd-stress sve-stress ssve-stress za-stress
|
| D | .gitignore | 2 fp-stress
|
| /Linux-v6.6/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-v6.6/Documentation/admin-guide/ |
| 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-ng>`_ to
176 * stress-ng
254 What is stress-ng and how do we use it?
257 As mentioned earlier, stress-ng is used for performing stress testing on
[all …]
|
| /Linux-v6.6/tools/testing/selftests/mm/ |
| D | .gitignore | 20 transhuge-stress
25 uffd-stress
|
| D | Makefile | 64 TEST_GEN_FILES += transhuge-stress
65 TEST_GEN_FILES += uffd-stress
121 $(OUTPUT)/uffd-stress: uffd-common.c
|
| D | uffd-stress.c | 179 static int stress(struct uffd_args *args) in stress() function
326 if (stress(args)) in userfaultfd_stress()
|
| D | run_vmtests.sh | 245 uffd_stress_bin=./uffd-stress
350 CATEGORY="thp" run_test ./transhuge-stress -d 20
|
| /Linux-v6.6/lib/ |
| 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-v6.6/tools/memory-model/Documentation/ |
| D | access-marking.txt | 520 When designing stress tests it is important to ensure that race conditions
550 invoked concurrently, the stress test should force this concurrency to
551 actually happen. KCSAN can evaluate the stress test when the above code
583 If a given stress-test run does not result in KCSAN complaints from
585 stress test needs improvement. If the stress test was to be evaluated
588 false positives when not evaluating the stress test.
|
| /Linux-v6.6/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 40 stress with multiple ports injecting line-rate traffic.
|
| /Linux-v6.6/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-v6.6/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-v6.6/Documentation/mm/ |
| D | hwpoison.rst | 152 value). This allows stress testing of many kinds of
|
| /Linux-v6.6/Documentation/power/regulator/ |
| D | consumer.rst | 180 consumers under regulator stress or failure conditions.
|
| /Linux-v6.6/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 272 2. If a regular CPU hotplug stress test happens to race with the freezer due
|
| /Linux-v6.6/Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 61 configurations using more than 4 planes. Again, it is important to stress that
|
| /Linux-v6.6/kernel/trace/ |
| D | Kconfig | 909 tristate "Ring buffer benchmark stress tester"
912 This option creates a test to stress the ring buffer and benchmark it.
1061 to the ring buffer, to test/stress the nesting ability.
|
| /Linux-v6.6/kernel/rcu/ |
| D | Kconfig | 152 systems, but if you are stress-testing the RCU implementation
|
| /Linux-v6.6/drivers/usb/misc/ |
| D | Kconfig | 205 with specialized device firmware for regression and stress testing,
|
| /Linux-v6.6/Documentation/core-api/ |
| D | pin_user_pages.rst | 66 field, refcount overflows were seen in some huge page stress tests.
|
