/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, \ 121 .fails = true, \ 149 .fails = true, \ 222 .fails = true, \ 262 .fails = true, \ 269 .fails = true, \ 310 .fails = true, \ 330 .fails = true, \ 349 .fails = true, \ [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.
|
/linux/drivers/gpu/drm/ci/xfails/ |
H A D | msm-apq8016-skips.txt | 14 # Currently fails and causes coverage loss for other tests 15 # since core_getversion also fails.
|
H A D | meson-g12b-skips.txt | 15 # Currently fails and causes coverage loss for other tests 16 # since core_getversion also fails.
|
H A D | mediatek-mt8183-skips.txt | 15 # Currently fails and causes coverage loss for other tests 16 # since core_getversion also fails.
|
H A D | mediatek-mt8173-skips.txt | 15 # Currently fails and causes coverage loss for other tests 16 # since core_getversion also fails.
|
H A D | msm-sc7180-trogdor-lazor-limozeen-skips.txt | 17 # Currently fails and causes coverage loss for other tests 18 # since core_getversion also fails.
|
H A D | rockchip-rk3399-skips.txt | 18 # Currently fails and causes coverage loss for other tests 19 # since core_getversion also fails.
|
H A D | rockchip-rk3288-skips.txt | 18 # Currently fails and causes coverage loss for other tests 19 # since core_getversion also fails.
|
H A D | panfrost-g12b-skips.txt | 21 # Currently fails and causes coverage loss for other tests 22 # since core_getversion also fails.
|
H A D | panfrost-mt8183-skips.txt | 21 # Currently fails and causes coverage loss for other tests 22 # since core_getversion also fails.
|
H A D | msm-sc7180-trogdor-kingoftown-skips.txt | 17 # Currently fails and causes coverage loss for other tests 18 # since core_getversion also fails.
|
H A D | virtio_gpu-none-skips.txt | 23 # Currently fails and causes coverage loss for other tests 24 # since core_getversion also fails.
|
H A D | panfrost-rk3399-skips.txt | 24 # Currently fails and causes coverage loss for other tests 25 # since core_getversion also fails.
|
H A D | panfrost-rk3288-skips.txt | 24 # Currently fails and causes coverage loss for other tests 25 # since core_getversion also fails.
|
H A D | msm-apq8096-skips.txt | 17 # Currently fails and causes coverage loss for other tests 18 # since core_getversion also fails.
|
H A D | msm-sdm845-skips.txt | 22 # Currently fails and causes coverage loss for other tests 23 # since core_getversion also fails.
|
H A D | amdgpu-stoney-skips.txt | 18 # Currently fails and causes coverage loss for other tests 19 # since core_getversion also fails.
|
/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 | 1725 static void print_footer_stdio(int total, int bad, struct lock_contention_fails *fails) in print_lock_stat_stdio() 1728 int broken = fails->task + fails->stack + fails->time + fails->data; in print_lock_stat_stdio() 1742 fprintf(lock_output, " %10s: %d\n", "task", fails->task); in print_lock_stat_stdio() 1743 fprintf(lock_output, " %10s: %d\n", "stack", fails->stack); in print_lock_stat_stdio() 1744 fprintf(lock_output, " %10s: %d\n", "time", fails->time); in print_lock_stat_stdio() 1745 fprintf(lock_output, " %10s: %d\n", "data", fails->data); in print_lock_stat_stdio() 1748 static void print_footer_csv(int total, int bad, struct lock_contention_fails *fails, in print_lock_stat_stdio() 1834 print_footer_stdio(int total,int bad,struct lock_contention_fails * fails) print_footer_stdio() argument 1857 print_footer_csv(int total,int bad,struct lock_contention_fails * fails,const char * sep) print_footer_csv() argument 1885 print_footer(int total,int bad,struct lock_contention_fails * fails) print_footer() argument [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,
|