| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | core_extern.c | 26 bool fails; member
60 { .name = "tristate (int)", .fails = 1, .cfg = CFG"CONFIG_TRISTATE=1" },
61 { .name = "tristate (bad)", .fails = 1, .cfg = CFG"CONFIG_TRISTATE=M" },
67 { .name = "bool (tristate)", .fails = 1, .cfg = CFG"CONFIG_BOOL=m" },
68 { .name = "bool (int)", .fails = 1, .cfg = CFG"CONFIG_BOOL=1" },
72 { .name = "char (bad)", .fails = 1, .cfg = CFG"CONFIG_CHAR=q\n" },
73 { .name = "char (empty)", .fails = 1, .cfg = CFG"CONFIG_CHAR=\n" },
74 { .name = "char (str)", .fails = 1, .cfg = CFG"CONFIG_CHAR=\"y\"\n" },
82 { .name = "str (no value)", .fails = 1, .cfg = CFG"CONFIG_STR=\n" },
83 { .name = "str (bad value)", .fails = 1, .cfg = CFG"CONFIG_STR=bla\n" },
[all …]
|
| H A D | core_reloc.c | 62 .fails = true, \
87 .fails = true, \
122 .fails = true, \
150 .fails = true, \
223 .fails = true, \
263 .fails = true, \
270 .fails = true, \
311 .fails = true, \
331 .fails = true, \
350 .fails
403 bool fails; global() member
[all...] |
| H A D | cpu_mask.c | 35 bool fails; member
66 if (test_cases[i].fails) { in test_cpu_mask()
|
| /linux/tools/perf/tests/ |
| H A D | bp_signal_overflow.c | 68 int fd, i, fails = 0; in test__bp_signal_overflow() local
131 fails++; in test__bp_signal_overflow()
137 fails++; in test__bp_signal_overflow()
140 return fails ? TEST_FAIL : TEST_OK; in test__bp_signal_overflow()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-platform-dfl-fme | 54 fails with -EINVAL if input parsing fails or input error code
63 fails with -EINVAL if input parsing fails or input error code
83 file to inject errors for testing purpose. Write fails with
84 -EINVAL if input parsing fails or input inject error code isn't
93 fails with -EINVAL if input parsing fails or input error code
197 clamped within the range from 0 to 127 Watts. Write fails with
198 -EINVAL if input parsing fails.
210 clamped within the range from 0 to 127 Watts. Write fails with
211 -EINVAL if input parsing fails.
|
| H A D | sysfs-platform-dfl-port | 84 to clear errors. Write fails with -EINVAL if input parsing
85 fails or input error code doesn't match. Write fails with
|
| H A D | sysfs-class-fpga-manager | 15 fails, that could be due to not being able to find the firmware
43 If FPGA programming operation fails, it could be caused by crc
|
| H A D | sysfs-class-rc | 40 Write fails with EINVAL if an invalid protocol combination or
97 Write fails with EINVAL if an invalid protocol combination or
|
| /linux/tools/testing/selftests/powerpc/papr_sysparm/ |
| H A D | papr_sysparm.c | 186 size_t fails = 0; in main() local
192 ++fails; in main()
195 return fails == 0 ? EXIT_SUCCESS : EXIT_FAILURE; in main()
|
| /linux/tools/perf/ |
| H A D | builtin-lock.c | 1739 static void print_footer_stdio(int total, int bad, struct lock_contention_fails *fails) in print_footer_stdio() argument
1742 int broken = fails->task + fails->stack + fails->time + fails->data; in print_footer_stdio()
1756 fprintf(lock_output, " %10s: %d\n", "task", fails->task); in print_footer_stdio()
1757 fprintf(lock_output, " %10s: %d\n", "stack", fails->stack); in print_footer_stdio()
1758 fprintf(lock_output, " %10s: %d\n", "time", fails->time); in print_footer_stdio()
1759 fprintf(lock_output, " %10s: %d\n", "data", fails->data); in print_footer_stdio()
1762 static void print_footer_csv(int total, int bad, struct lock_contention_fails *fails, in print_footer_csv() argument
1767 bad = fails->task + fails->stack + fails->time + fails->data; in print_footer_csv()
1776 fprintf(lock_output, "%s bad_%s=%d", sep, "task", fails->task); in print_footer_csv()
1777 fprintf(lock_output, "%s bad_%s=%d", sep, "stack", fails->stack); in print_footer_csv()
[all …]
|
| /linux/tools/testing/selftests/timers/ |
| H A D | freq-step.c | 241 int i, j, fails = 0; in main() local
253 fails += run_test(0, freq_base, freq_step); in main()
259 if (fails) in main()
|
| /linux/Documentation/power/ |
| H A D | basic-pm-debugging.rst | 23 fails to hibernate or resume in the "reboot" mode, you should try the
47 To find out why hibernation fails on your system, you can use a special testing
103 without creating a hibernation image. Obviously, if the "devices" test fails,
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
115 If the "devices" test fails, most likely there is a driver that cannot suspend
120 - if the test fails, unload a half of the drivers currently loaded and repeat
136 If the "platform" test fails, there is a problem with the handling of the
141 If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
147 If the "core" test fails, which means that suspending of the system/platform
168 - if there are n modules loaded and the attempt to suspend and resume fails,
|
| /linux/tools/testing/selftests/powerpc/papr_vpd/ |
| H A D | papr_vpd.c | 342 size_t fails = 0; in main() local
348 ++fails; in main()
351 return fails == 0 ? EXIT_SUCCESS : EXIT_FAILURE; in main()
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | mmp.rst | 12 fsck is (hopefully) running, and open fails immediately. Otherwise, the
15 filesystem is active on another machine and the open fails. If the MMP
|
| /linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-am62p-verdin-wifi.dtsi | 29 ti,fails-without-test-cd;
|
| H A D | k3-am62-verdin-wifi.dtsi | 28 ti,fails-without-test-cd;
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | transhuge.rst | 428 huge pages if the PMD-sized huge page allocation fails;
438 huge pages if the PMD-sized huge page allocation fails;
544 is incremented if a page fault fails to allocate or charge
548 is incremented if a page fault fails to charge a huge page and
564 but fails and instead falls back to using small pages. (Note that
584 is incremented if kernel fails to split huge
611 is incremented if kernel fails to allocate
633 is incremented if a page fault fails to allocate or charge
638 is incremented if a page fault fails to charge a huge page and
651 is incremented if swapin fails to allocate or charge a huge page
[all …]
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 90 If the lock-acquire fastpath fails, [i.e. an atomic transition from 0 to
91 TID fails], then FUTEX_LOCK_PI is called. The kernel does all the
108 If the unlock fastpath fails (because the FUTEX_WAITERS bit is set),
|
| /linux/tools/perf/util/ |
| H A D | bpf_lock_contention.c | 731 con->fails.task = skel->bss->task_fail; in lock_contention_read()
732 con->fails.stack = skel->bss->stack_fail; in lock_contention_read()
733 con->fails.time = skel->bss->time_fail; in lock_contention_read()
734 con->fails.data = skel->bss->data_fail; in lock_contention_read()
|
| H A D | lock-contention.h | 150 struct lock_contention_fails fails; member
|
| /linux/drivers/of/unittest-data/ |
| H A D | overlay_bad_add_dup_prop.dtso | 19 * fails, the memory leak does actually occur, and kmemleak will
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | func-poll.rst | 68 capturing. When that fails it returns a ``POLLERR`` as above. Otherwise
75 streaming. When that fails it returns a ``POLLERR`` as above. Otherwise
|
| H A D | func-ioctl.rst | 57 When an ioctl that takes an output or read/write parameter fails, the
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | fe-get-event.rst | 38 or non-blocking mode. In the latter case, the call fails immediately
|
| /linux/Documentation/core-api/ |
| H A D | boot-time-mm.rst | 19 when an allocation fails and those that don't.
|