Home
last modified time | relevance | path

Searched refs:failures (Results 1 – 25 of 120) sorted by relevance

12345

/linux-6.6.21/lib/
Dtest_meminit.c20 if (failures) \
22 __func__, failures, num_tests); \
93 int failures = 0, num_tests = 0; in test_pages() local
97 num_tests += do_alloc_pages_order(i, &failures); in test_pages()
100 *total_failures += failures; in test_pages()
155 int failures = 0, num_tests = 0; in test_kvmalloc() local
160 num_tests += do_kmalloc_size(size, &failures); in test_kvmalloc()
161 num_tests += do_vmalloc_size(size, &failures); in test_kvmalloc()
165 *total_failures += failures; in test_kvmalloc()
380 int failures = 0, num_tests = 0; in test_kmemcache() local
[all …]
/linux-6.6.21/tools/testing/selftests/kvm/x86_64/
Dtsc_scaling_sync.c46 unsigned long failures = 0; in run_vcpu() local
75 failures++; in run_vcpu()
83 return (void *)failures; in run_vcpu()
99 unsigned long failures = 0; in main() local
103 failures += (unsigned long)this_cpu_failures; in main()
106 TEST_ASSERT(!failures, "TSC sync failed"); in main()
/linux-6.6.21/tools/testing/selftests/bpf/
Dtest_xsk.sh194 failures=0
200 failures=1
204 if [ $failures -eq 0 ]; then
DREADME.rst15 are propagated to patchwork, where failures are highlighted similar to
90 Additional information about selftest failures are
93 profiler[23] test failures with clang/llvm <12.0.0
132 bpf_iter test failures with clang/llvm 10.0.0
218 old to support them, they shouldn't cause build failures or runtime test
219 failures:
/linux-6.6.21/tools/testing/selftests/mm/
Dmremap_test.c368 static void run_mremap_test_case(struct test test_case, int *failures, in run_mremap_test_case() argument
381 *failures += 1; in run_mremap_test_case()
441 int failures = 0; in main() local
521 run_mremap_test_case(test_cases[i], &failures, threshold_mb, in main()
540 run_mremap_test_case(perf_test_cases[i], &failures, in main()
544 if (failures > 0) in main()
/linux-6.6.21/drivers/md/
Ddm-raid1.c67 struct bio_list failures; member
646 if (!ms->failures.head) in write_callback()
648 bio_list_add(&ms->failures, bio); in write_callback()
772 bio_list_merge(&ms->failures, &sync); in do_writes()
785 bio_list_add(&ms->failures, bio); in do_writes()
795 static void do_failures(struct mirror_set *ms, struct bio_list *failures) in do_failures() argument
799 if (likely(!failures->head)) in do_failures()
819 while ((bio = bio_list_pop(failures))) { in do_failures()
864 struct bio_list reads, writes, failures; in do_mirror() local
870 failures = ms->failures; in do_mirror()
[all …]
/linux-6.6.21/Documentation/fault-injection/
Dfault-injection.rst13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
21 injects failures in user memory access functions. (copy_from_user(), get_user(), ...)
29 injects kernel RPC client and server failures.
85 specifies the interval between failures, for calls to
93 specifies how many times failures may happen at most. A value of -1
116 Any positive value limits failures to only processes indicated by
141 default is 'Y', setting it to 'N' will also inject failures into
149 default is 'Y', setting it to 'N' will also inject failures
155 failures.
[all …]
/linux-6.6.21/tools/testing/selftests/net/
Drxtimestamp.c361 int failures = 0; in main() local
420 failures++; in main()
424 failures++; in main()
427 if (!failures) in main()
429 return failures; in main()
/linux-6.6.21/tools/perf/tests/
Dpmu-events.c811 int *failures = data; in test__parsing_callback() local
825 (*failures)++; in test__parsing_callback()
847 (*failures)--; in test__parsing_callback()
880 (*failures)--; in test__parsing_callback()
902 int failures = 0; in test__parsing() local
904 pmu_for_each_core_metric(test__parsing_callback, &failures); in test__parsing()
905 pmu_for_each_sys_metric(test__parsing_callback, &failures); in test__parsing()
907 return failures == 0 ? TEST_OK : TEST_FAIL; in test__parsing()
/linux-6.6.21/tools/testing/fault-injection/
Dfailcmd.sh31 specifies how many times failures may happen at most.
59 inject slab allocation failures
61 inject page allocation failures
/linux-6.6.21/tools/perf/tests/shell/lib/
Dperf_metric_validation.py274 failures = dict()
282 failures[m['Name']] = result
289 if name not in failures: continue
292 del failures[name]
294 failures[name] = val
301 if len(failures.keys()) != 0:
302 faillist = [{'MetricName':name, 'CollectedValue':val} for name, val in failures.items()]
/linux-6.6.21/tools/testing/selftests/rcutorture/bin/
Dkvm-check-branches.sh97 echo '!!! ' $nfail failures in $ntry 'runs!!!'
100 echo No failures in $ntry runs.
Dtorture.sh265 touch $T/failures
301 echo "$curflavor($retcode)" $resdir >> $T/failures
372 echo "allmodconfig($retcode)" $amcdir >> $T/failures
406 echo "rcutasksflavors($retcode)" $rtfdir >> $T/failures
455 …lockdep($retcode)" "tools/testing/selftests/rcutorture/res/$ds/results-srcu-lockdep" >> $T/failures
596 nfailures="`wc -l "$T/failures" | awk '{ print $1 }'`"
/linux-6.6.21/Documentation/mm/
Dhwpoison.rst29 users, because memory failures could happen anytime and anywhere,
51 memory failures too. The expectation is that most applications
60 All memory failures cause a panic. Do not attempt recovery.
121 injected failures, not for real memory failures. Once any hardware
128 Only handle memory failures to pages associated with the file
/linux-6.6.21/arch/x86/kernel/cpu/sgx/
Dvirt.c157 long failures = 0; in sgx_vepc_remove_all() local
164 failures++; in sgx_vepc_remove_all()
185 return failures; in sgx_vepc_remove_all()
/linux-6.6.21/tools/testing/selftests/x86/
Dldt_gdt.c534 int failures = 0, iters = 5, i; in do_multicpu_tests() local
608 failures++; in do_multicpu_tests()
618 if (failures) { in do_multicpu_tests()
619 printf("[FAIL]\t%d of %d iterations failed\n", failures, iters); in do_multicpu_tests()
/linux-6.6.21/drivers/net/ethernet/i825xx/
Dether1.c447 int failures = 0; in ether1_init_for_open() local
537 failures += 1; in ether1_init_for_open()
554 failures += 1; in ether1_init_for_open()
571 failures += 1; in ether1_init_for_open()
604 if (failures) in ether1_init_for_open()
606 return failures ? 1 : 0; in ether1_init_for_open()
/linux-6.6.21/drivers/platform/x86/amd/pmc/
DKconfig15 mechanism to investigate the S2Idle transactions and failures.
/linux-6.6.21/tools/testing/ktest/examples/include/
Ddefaults.conf151 STORE_FAILURES = ${THIS_DIR}/failures
/linux-6.6.21/drivers/gpu/drm/ci/
Digt_runner.sh68 --results /results/failures.csv \
/linux-6.6.21/scripts/coccinelle/api/
Dplatform_get_irq.cocci2 /// Remove dev_err() messages after platform_get_irq*() failures
/linux-6.6.21/Documentation/core-api/
Ddma-attributes.rst113 On some architectures allocation failures are reported with error messages
115 drivers which handle failures (eg, retry later) have no problems with them,
120 where allocation failures are not a problem, and shouldn't bother the logs.
/linux-6.6.21/drivers/usb/image/
DKconfig26 Please report failures and successes.
/linux-6.6.21/Documentation/admin-guide/device-mapper/
Ddm-queue-length.rst23 <fail-count>: The number of path failures.
/linux-6.6.21/tools/testing/kunit/
Dkunit_parser.py596 failures = failed_names(test, '')
598 if len(failures) > 10: # this is an arbitrary limit
601 return 'Failures: ' + ', '.join(failures)

12345