| /Linux-v6.6/tools/testing/selftests/bpf/prog_tests/ |
| 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 …]
|
| D | core_reloc.c | 61 .fails = true, \
86 .fails = true, \
120 .fails = true, \
148 .fails = true, \
221 .fails = true, \
261 .fails = true, \
268 .fails = true, \
309 .fails = true, \
329 .fails = true, \
348 .fails = true, \
[all …]
|
| D | cpu_mask.c | 35 bool fails; member
66 if (test_cases[i].fails) { in test_cpu_mask()
|
| D | bpf_verif_scale.c | 51 bool fails; member
|
| /Linux-v6.6/tools/perf/tests/ |
| D | bp_signal_overflow.c | 67 int fd, i, fails = 0; in test__bp_signal_overflow() local
130 fails++; in test__bp_signal_overflow()
136 fails++; in test__bp_signal_overflow()
139 return fails ? TEST_FAIL : TEST_OK; in test__bp_signal_overflow()
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| 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.
|
| 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
|
| 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
|
| /Linux-v6.6/tools/perf/ |
| D | builtin-lock.c | 1804 static void print_footer_stdio(int total, int bad, struct lock_contention_fails *fails) in print_footer_stdio() argument
1807 int broken = fails->task + fails->stack + fails->time + fails->data; in print_footer_stdio()
1821 fprintf(lock_output, " %10s: %d\n", "task", fails->task); in print_footer_stdio()
1822 fprintf(lock_output, " %10s: %d\n", "stack", fails->stack); in print_footer_stdio()
1823 fprintf(lock_output, " %10s: %d\n", "time", fails->time); in print_footer_stdio()
1824 fprintf(lock_output, " %10s: %d\n", "data", fails->data); in print_footer_stdio()
1827 static void print_footer_csv(int total, int bad, struct lock_contention_fails *fails, in print_footer_csv() argument
1832 bad = fails->task + fails->stack + fails->time + fails->data; in print_footer_csv()
1841 fprintf(lock_output, "%s bad_%s=%d", sep, "task", fails->task); in print_footer_csv()
1842 fprintf(lock_output, "%s bad_%s=%d", sep, "stack", fails->stack); in print_footer_csv()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/timers/ |
| 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-v6.6/Documentation/power/ |
| 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-v6.6/Documentation/driver-api/tty/ |
| D | tty_ldisc.rst | 11 fallback if establishing any other discipline for a tty fails. If even N_TTY
12 fails, N_NULL takes over. That never fails, but also does not process any
|
| /Linux-v6.6/tools/perf/util/ |
| D | bpf_lock_contention.c | 262 con->fails.task = skel->bss->task_fail; in lock_contention_read()
263 con->fails.stack = skel->bss->stack_fail; in lock_contention_read()
264 con->fails.time = skel->bss->time_fail; in lock_contention_read()
265 con->fails.data = skel->bss->data_fail; in lock_contention_read()
|
| D | lock-contention.h | 138 struct lock_contention_fails fails; member
|
| /Linux-v6.6/tools/testing/selftests/bpf/ |
| D | test_sock.c | 521 int fails = 0; in run_tests() local
526 ++fails; in run_tests()
530 printf("Summary: %d PASSED, %d FAILED\n", passes, fails); in run_tests()
531 return fails ? -1 : 0; in run_tests()
|
| /Linux-v6.6/tools/perf/tests/attr/ |
| D | test-record-user-regs-no-sve-aarch64 | 1 # Test that asking for VG fails if the system doesn't support SVE. This
|
| D | test-record-user-regs-old-sve-aarch64 | 1 # Test that asking for VG always fails on old kernels because it was
|
| /Linux-v6.6/Documentation/filesystems/ext4/ |
| 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-v6.6/arch/arm64/boot/dts/ti/ |
| D | k3-am62-verdin-wifi.dtsi | 28 ti,fails-without-test-cd;
|
| /Linux-v6.6/drivers/gpu/drm/ci/ |
| D | arm.config | 10 # abootimg with a 'dummy' rootfs fails with root=/dev/nfs
|
| /Linux-v6.6/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-skips.txt | 21 # failure mode is flakey due to randomization but fails frequently
|
| /Linux-v6.6/Documentation/networking/ |
| D | netdevices.rst | 139 /* If anything fails now unregister_netdevice() (or unregister_netdev())
154 register_netdevice() fails. The callback may be invoked with or without
163 so if register_netdevice() fails driver is responsible for calling
167 or when register_netdevice() fails. Parts of netdev (de)registration process
|
| /Linux-v6.6/drivers/of/unittest-data/ |
| D | overlay_bad_add_dup_prop.dtso | 19 * fails, the memory leak does actually occur, and kmemleak will
|
| /Linux-v6.6/Documentation/locking/ |
| 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-v6.6/fs/afs/ |
| D | Kconfig | 38 the dmesg log if the server rotation algorithm fails to successfully
|
