| /linux/kernel/trace/ |
| H A D | trace_branch.c | 221 f->data.incorrect++; in ftrace_likely_update()
246 percent = p->incorrect * 100; in get_incorrect_percent()
247 percent /= p->correct + p->incorrect; in get_incorrect_percent()
249 percent = p->incorrect ? 100 : -1; in get_incorrect_percent()
286 seq_printf(m, "%8lu %8lu ", p->correct, p->incorrect); in branch_stat_show_normal()
306 p->data.correct, p->constant, l, p->data.incorrect); in annotate_branch_stat_show()
344 if (a->incorrect < b->incorrect) in annotated_branch_stat_cmp()
346 if (a->incorrect > b->incorrect) in annotated_branch_stat_cmp()
|
| /linux/arch/loongarch/ |
| H A D | Kconfig.debug | 14 finds. Some of the addresses it reports may be incorrect.
26 Some of the addresses it reports may be incorrect (but better than the
|
| /linux/drivers/atm/ |
| H A D | nicstar.h | 580 #error NS_SMBUFSIZE is incorrect in nicstar.h
592 #error NS_LGBUFSIZE is incorrect in nicstar.h
602 #error NS_RSQSIZE is incorrect in nicstar.h
614 #error NS_VPIBITS is incorrect in nicstar.h
|
| /linux/arch/m68k/fpsp040/ |
| H A D | x_operr.S | 162 bnes chkwerr |if not equal, check for incorrect operr
165 bnes chkwerr |if d0 is true, check for incorrect operr
189 bnes chkberr |if not equal, check for incorrect operr
192 bnes chkberr |if d0 is true, check for incorrect operr
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-munmap.rst | 51 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | func-munmap.rst | 53 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /linux/arch/arm/boot/dts/synaptics/ |
| H A D | berlin2cd-google-chromecast.dts | 28 * with this device provides an incorrect memory range in
|
| /linux/Documentation/pcmcia/ |
| H A D | devicetable.rst | 23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 78 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
100 * incorrect value if VCC_1V8_S0_1 isn't properly routed,
|
| /linux/Documentation/process/debugging/ |
| H A D | index.rst | 61 consistently (i.e. given a set of inputs you always get the same, incorrect
|
| /linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm53016-meraki-mr32.dts | 131 * It will only detect the "nvram" partition with an incorrect size.
|
| H A D | bcm47094-dlink-dir-890l.dts | 147 * assume. The CFE loader contains incorrect information
|
| /linux/Documentation/driver-api/cxl/platform/ |
| H A D | acpi.rst | 60 * CEDT CHBS Specification version is incorrect.
|
| /linux/Documentation/userspace-api/ |
| H A D | spec_ctrl.rst | 81 ERANGE arg3 is incorrect, i.e. it's neither PR_SPEC_ENABLE nor
|
| /linux/Documentation/driver-api/md/ |
| H A D | raid5-ppl.rst | 12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
|
| /linux/Documentation/dev-tools/ |
| H A D | kmsan.rst | 95 incorrect shadow/origin values, likely leading to false positives. Functions
96 called from non-instrumented code may also receive incorrect metadata for their
396 corrupt other pages or read incorrect values from them.
|
| /linux/include/linux/ |
| H A D | compiler_types.h | 197 unsigned long incorrect; member
|
| /linux/arch/arm64/boot/dts/freescale/ |
| H A D | fsl-ls1028a-tqmls1028a-mbls1028a.dtsi | 170 * Long reset to work around PHY incorrect strap pin sampling
|
| /linux/arch/m68k/math-emu/ |
| H A D | fp_entry.S | 112 | instruction decoding, otherwise the stack pointer is incorrect
|
| /linux/Documentation/networking/ |
| H A D | ila.rst | 117 incorrect on the wire. This is a problem for intermediate devices,
121 - no action Allow the checksum to be incorrect on the wire. Before
|
| /linux/Documentation/filesystems/ |
| H A D | ocfs2-online-filecheck.rst | 28 In case of directory to file links is incorrect, the directory inode is
|
| /linux/arch/arm64/ |
| H A D | Kconfig | 637 bool "Cortex-A53: 845719: a load might read incorrect data"
647 might return incorrect data.
658 bool "Cortex-A53: 843419: A load or store might access an incorrect address"
663 cause subsequent memory accesses to use an incorrect address on
669 …tex-A55: 1024718: Update of DBM/AP bits without break before make might result in incorrect update"
674 Affected Cortex-A55 cores (all revisions) could cause incorrect
683 …-N1: MRC read following MRRC read of specific Generic Timer in AArch32 might give incorrect result"
700 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
713 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
726 …-of-context translation regime could cause subsequent request to generate an incorrect translation"
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-c2c.txt | 136 where it creates incorrect call stacks from incorrect matches.
|
| /linux/Documentation/process/ |
| H A D | generated-content.rst | 103 As with the output of any tooling, the result may be incorrect or
|
| /linux/arch/powerpc/platforms/8xx/ |
| H A D | Kconfig | 116 This bug can cause incorrect code execution under certain
|