Home
last modified time | relevance | path

Searched full:warnings (Results 1 – 25 of 815) sorted by relevance

12345678910>>...33

/kernel/linux/linux-4.19/Documentation/RCU/
Dstallwarn.txt9 What Causes RCU CPU Stall Warnings?
13 warnings:
69 RCU CPU stall warnings.
72 timeout down to just barely avoid RCU CPU stall warnings, and then
80 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
87 This resulted in a series of RCU CPU stall warnings, eventually
91 warning. Note that SRCU does -not- have CPU stall warnings. Please note
93 No grace period, no CPU stall warnings.
97 If you have a series of stall warnings from a single extended stall,
147 own warnings, as this often gives better-quality stack traces.
[all …]
/kernel/linux/linux-5.10/Documentation/RCU/
Dstallwarn.rst13 What Causes RCU CPU Stall Warnings?
18 warnings:
77 RCU CPU stall warnings.
80 timeout down to just barely avoid RCU CPU stall warnings, and then
88 result in RCU CPU stall warnings for CONFIG_NO_HZ_COMMON=n kernels.
102 This resulted in a series of RCU CPU stall warnings, eventually
106 Note that SRCU does -not- have CPU stall warnings. Please note that
108 No grace period, no CPU stall warnings.
112 If you have a series of stall warnings from a single extended stall,
166 own warnings, as this often gives better-quality stack traces.
[all …]
/kernel/linux/linux-5.10/Documentation/doc-guide/
Dcontributing.rst30 Addressing warnings
34 warnings. When you have that many, you might as well have none at all;
36 ones. For this reason, eliminating warnings is one of the highest-priority
41 Warnings issued by a compiler for C code can often be dismissed as false
43 Warnings from the documentation build almost always point at a real
44 problem; making those warnings go away requires understanding the problem
46 warnings should probably not say "fix a warning" in the changelog title;
49 Another important point is that documentation warnings are often created by
51 maintainer appreciates being copied on fixes for these warnings, the
55 For example, in a documentation build I grabbed a pair of warnings nearly
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/kvm/x86_64/
Dmmio_warning_test.c81 int warnings; in get_warnings_count() local
85 if (fscanf(f, "%d", &warnings) < 1) in get_warnings_count()
86 warnings = 0; in get_warnings_count()
89 return warnings; in get_warnings_count()
124 "Warnings found in kernel. Run 'dmesg' to inspect them."); in main()
/kernel/linux/linux-4.19/lib/
Ddebugobjects.c827 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
975 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1001 if (warnings != debug_objects_warnings) { in check_results()
1002 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1003 warnings, debug_objects_warnings); in check_results()
1027 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1033 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1037 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1040 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1043 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
/kernel/linux/linux-4.19/tools/testing/ktest/examples/include/
Dpatchcheck.conf56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
/kernel/linux/linux-5.10/tools/testing/ktest/examples/include/
Dpatchcheck.conf56 # Instead of just checking for warnings to files that are changed
57 # it can be advantageous to check for any new warnings. If a
59 # touched by the commit. To detect these kinds of warnings, you
65 # warnings file.
74 # and record all the warnings that exist before the patches
/kernel/linux/linux-4.19/include/uapi/linux/
Ddqblk_xfs.h67 __u16 d_iwarns; /* # warnings issued wrt num inodes */
68 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
74 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
104 * warnings are set/cleared by the administrators (or automatically by going
165 __u16 qs_bwarnlimit; /* limit for num warnings */
166 __u16 qs_iwarnlimit; /* limit for num warnings */
210 __u16 qs_bwarnlimit; /* limit for num warnings */
211 __u16 qs_iwarnlimit; /* limit for num warnings */
/kernel/linux/linux-5.10/drivers/base/test/
Dtest_async_driver_probe.c21 static atomic_t warnings, errors, timeout, async_completed; variable
51 atomic_inc(&warnings); in test_probe()
244 * Otherwise if they completed without errors or warnings then in test_async_probe_init()
251 } else if (!atomic_read(&errors) && !atomic_read(&warnings)) { in test_async_probe_init()
271 * errors or warnings being reported by the probe routine. in test_async_probe_init()
278 pr_err("Test failed with %d errors and %d warnings\n", in test_async_probe_init()
279 atomic_read(&errors), atomic_read(&warnings)); in test_async_probe_init()
/kernel/linux/linux-5.10/lib/
Ddebugobjects.c1033 seq_printf(m, "warnings :%d\n", debug_objects_warnings); in debug_stats_show()
1161 check_results(void *addr, enum debug_obj_state state, int fixups, int warnings) in check_results() argument
1187 if (warnings != debug_objects_warnings) { in check_results()
1188 WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n", in check_results()
1189 warnings, debug_objects_warnings); in check_results()
1213 int fixups, oldfixups, warnings, oldwarnings; in debug_objects_selftest() local
1219 warnings = oldwarnings = debug_objects_warnings; in debug_objects_selftest()
1223 if (check_results(&obj, ODEBUG_STATE_INIT, fixups, warnings)) in debug_objects_selftest()
1226 if (check_results(&obj, ODEBUG_STATE_ACTIVE, fixups, warnings)) in debug_objects_selftest()
1229 if (check_results(&obj, ODEBUG_STATE_ACTIVE, ++fixups, ++warnings)) in debug_objects_selftest()
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh140 echo CPU count limited from $cpu_count to $TORTURE_ALLOTED_CPUS | tee -a $resdir/Warnings
218 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
219 grep "^(qemu) qemu:" $resdir/kvm-test-1-run.sh.out >> $resdir/Warnings 2>&1
220 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
223 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
224 ps -fp $killpid >> $resdir/Warnings 2>&1
247 echo "PID $qemu_pid killed due to run STOP request" >> $resdir/Warnings 2>&1
275 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
Dparse-build.sh39 grep warning: < $F > $T/warnings
40 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
41 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
/kernel/linux/linux-5.10/include/uapi/linux/
Ddqblk_xfs.h68 __u16 d_iwarns; /* # warnings issued wrt num inodes */
69 __u16 d_bwarns; /* # warnings issued wrt disk blocks */
78 __u16 d_rtbwarns; /* # warnings issued wrt RT disk blks */
108 * warnings are set/cleared by the administrators (or automatically by going
175 __u16 qs_bwarnlimit; /* limit for num warnings */
176 __u16 qs_iwarnlimit; /* limit for num warnings */
220 __u16 qs_bwarnlimit; /* limit for num warnings */
221 __u16 qs_iwarnlimit; /* limit for num warnings */
/kernel/linux/linux-5.10/tools/power/acpi/
DMakefile.config64 WARNINGS := -Wall
65 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
71 CFLAGS += $(WARNINGS)
/kernel/linux/linux-4.19/tools/power/acpi/
DMakefile.config68 WARNINGS := -Wall
69 WARNINGS += $(call cc-supports,-Wstrict-prototypes)
70 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
75 CFLAGS += $(WARNINGS)
/kernel/linux/linux-5.10/scripts/
DMakefile.extrawarn21 # W=1 - warnings which may be relevant and do not occur too often
35 # The following turn off the warnings enabled by -Wextra
59 # W=2 - warnings which occur quite often but may still be relevant
77 # W=3 - more obscure warnings, can most likely be ignored
/kernel/linux/linux-4.19/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh158 echo CPU count limited from $cpu_count to $vcpus | tee -a $resdir/Warnings
211 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
212 grep "^(qemu) qemu:" $resdir/kvm-test-1-run.sh.out >> $resdir/Warnings 2>&1
213 …ed -n "s/^(qemu) qemu: terminating on signal [0-9]* from pid \([0-9]*\).*$/\1/p" $resdir/Warnings`"
216 echo "ps -fp $killpid" >> $resdir/Warnings 2>&1
217 ps -fp $killpid >> $resdir/Warnings 2>&1
259 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
Dparse-build.sh52 grep warning: < $F > $T/warnings
53 grep "include/linux/*rcu*\.h:" $T/warnings > $T/hwarnings
54 grep "kernel/rcu/[^/]*:" $T/warnings > $T/cwarnings
/kernel/linux/linux-5.10/fs/quota/
DKconfig26 If you say Y here, quota warnings (about exceeding softlimit, reaching
31 bool "Print quota warnings to console (OBSOLETE)"
35 If you say Y here, quota warnings (about exceeding softlimit, reaching
/kernel/linux/linux-4.19/fs/quota/
DKconfig25 If you say Y here, quota warnings (about exceeding softlimit, reaching
30 bool "Print quota warnings to console (OBSOLETE)"
34 If you say Y here, quota warnings (about exceeding softlimit, reaching
/kernel/linux/linux-4.19/drivers/gpu/drm/i915/
DMakefile9 # need to filter out dubious warnings. Still it is our interest
14 # new warnings before CI updates!
21 # clang warnings
27 # Fine grained warnings disable
/kernel/linux/linux-4.19/tools/usb/
DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(WARNINGS) -g -I../include
/kernel/linux/linux-4.19/tools/usb/ffs-aio-example/simple/host_app/
DMakefile4 WARNINGS = -Wall -Wextra macro
5 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/kernel/linux/linux-5.10/tools/usb/ffs-aio-example/simple/host_app/
DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)
/kernel/linux/linux-4.19/tools/usb/ffs-aio-example/multibuff/host_app/
DMakefile5 WARNINGS = -Wall -Wextra macro
6 CFLAGS = $(LIBUSB_CFLAGS) $(WARNINGS)

12345678910>>...33