| /linux/kernel/locking/ |
| A 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
469 kfree(stress); in stress_inorder_work()
479 struct stress *stress = container_of(work, typeof(*stress), work); in stress_reorder_work() local
534 kfree(stress); in stress_reorder_work()
539 struct stress *stress = container_of(work, typeof(*stress), work); in stress_one_work() local
556 kfree(stress); in stress_one_work()
577 struct stress *stress; in stress() local
599 stress = kmalloc(sizeof(*stress), GFP_KERNEL); in stress()
[all …]
|
| /linux/tools/testing/selftests/powerpc/security/ |
| A D | mitigation-patching.sh | 52 if stress-ng > /dev/null 2>&1; then
53 stress="stress-ng"
54 elif stress > /dev/null 2>&1; then
55 stress="stress"
57 stress=""
60 if [[ -n "$stress" ]]; then
61 "$stress" -m "$(nproc)" -t "$TIMEOUT" &
|
| /linux/tools/testing/selftests/arm64/fp/ |
| 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 …]
|
| A D | Makefile | 5 TEST_PROGS_EXTENDED := fpsimd-test fpsimd-stress \
7 sve-test sve-stress \
|
| /linux/tools/testing/selftests/prctl/ |
| A D | .gitignore | 2 disable-tsc-ctxt-sw-stress-test
3 disable-tsc-on-off-stress-test
|
| A D | Makefile | 7 TEST_PROGS := disable-tsc-ctxt-sw-stress-test disable-tsc-on-off-stress-test \
|
| /linux/tools/testing/selftests/vm/ |
| A D | .gitignore | 14 transhuge-stress
|
| A D | Makefile | 46 TEST_GEN_FILES += transhuge-stress
|
| A D | userfaultfd.c | 817 static int stress(struct uffd_stats *uffd_stats) in stress() function
1504 if (stress(uffd_stats)) in userfaultfd_stress()
|
| /linux/lib/ |
| A D | Kconfig.kfence | 69 this option is to stress test KFENCE with concurrent error reports
70 and allocations/frees. A value of 0 disables stress testing logic.
|
| /linux/tools/memory-model/Documentation/ |
| A 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/Documentation/locking/ |
| 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/drivers/net/ethernet/freescale/fman/ |
| A D | Kconfig | 39 stress with multiple ports injecting line-rate traffic.
|
| /linux/Documentation/admin-guide/cifs/ |
| A D | authors.rst | 69 …and SuSE and Citrix and RedHat testers for finding multiple bugs during excellent stress test runs.
|
| /linux/Documentation/vm/ |
| A D | hwpoison.rst | 155 value). This allows stress testing of many kinds of
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| A 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
|
| A D | iavf.rst | 315 'Page allocation failure. order:0' errors may occur under stress.
|
| /linux/Documentation/power/regulator/ |
| A D | consumer.rst | 180 consumers under regulator stress or failure conditions.
|
| /linux/kernel/rcu/ |
| A D | Kconfig | 130 systems, but if you are stress-testing the RCU implementation
|
| /linux/kernel/trace/ |
| A D | Kconfig | 789 tristate "Ring buffer benchmark stress tester"
792 This option creates a test to stress the ring buffer and benchmark it.
927 to the ring buffer, to test/stress the nesting ability.
|
| /linux/drivers/usb/misc/ |
| A D | Kconfig | 187 with specialized device firmware for regression and stress testing,
|
| /linux/Documentation/power/ |
| A D | suspend-and-cpuhotplug.rst | 272 2. If a regular CPU hotplug stress test happens to race with the freezer due
|
| /linux/Documentation/core-api/ |
| A D | pin_user_pages.rst | 67 page overflows were seen in some huge page stress tests.
|
| /linux/Documentation/admin-guide/pm/ |
| A 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/net/ |
| A D | Kconfig | 336 stress testing and performance analysis. If you don't understand
|