| /linux/Documentation/networking/ |
| A D | udplite.rst | 58 using partial checksum coverage and so emulate UDP mode (full coverage).
63 * Sender checksum coverage: UDPLITE_SEND_CSCOV
76 * Receiver checksum coverage: UDPLITE_RECV_CSCOV
83 packets with a minimum coverage of 20 are admitted::
124 assumes full coverage, transmits a packet with coverage length of 0
128 length is used instead as coverage length.
204 *****checksum coverage*************
230 coverage lengths are likely to be expected.
253 coverage length exceeds received length)
255 * application has specified larger min. coverage
[all …]
|
| A D | dccp.rst | 112 partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
117 DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
118 range 0..15 are acceptable. The default setting is 0 (full coverage),
119 values between 1..15 indicate partial coverage.
123 of 0 means that all packets with a partial coverage will be discarded.
125 coverage value are also acceptable. The higher the number, the more
126 restrictive this setting (see [RFC 4340, sec. 9.2.1]). Partial coverage
|
| /linux/Documentation/dev-tools/ |
| A D | kcov.rst | 1 kcov: code coverage for fuzzing
4 kcov exposes kernel code coverage information in a form suitable for coverage-
7 basis, and thus it can capture precise coverage of a single system call.
11 To achieve this goal it does not collect coverage in soft/hard interrupts
68 /* A single fd descriptor allows coverage collection on a single
82 /* Enable coverage collection on the current thread. */
85 /* Reset coverage from the tail of the ioctl() call. */
94 * coverage can be enabled for a different thread.
134 Comparison operands collection is similar to coverage collection:
211 Remote coverage collection
[all …]
|
| A D | gcov.rst | 4 gcov profiling kernel support enables the use of GCC's coverage testing
7 To get coverage data for a specific file, change to the kernel build
16 for the entire kernel and provide coverage overviews in HTML format.
26 .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
37 and to get coverage data for the entire kernel::
87 Global reset file: resets all coverage data to zero when
92 tool. Resets file coverage data to zero when written to.
97 option ``-ftest-coverage``.
169 [user@build] gcov -o /tmp/coverage/tmp/out/init main.c
217 Sample script to gather coverage meta files on the build machine
[all …]
|
| A D | testing-overview.rst | 69 The Linux Kernel supports two different code coverage measurement tools. These
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
75 used with the kernel to get global or per-module coverage. Unlike KCOV, it
76 does not record per-task coverage. Coverage data can be read from debugfs,
80 kernel to allow capturing coverage on a per-task level. It's therefore useful
|
| /linux/arch/arm/probes/kprobes/ |
| A D | test-core.c | 703 struct coverage_table coverage; variable
738 struct coverage_entry *entry = coverage->base + coverage->num_entries; in coverage_start_fn()
745 ++coverage->num_entries; in coverage_start_fn()
749 entry->nesting = coverage->nesting; in coverage_start_fn()
755 ++coverage->nesting; in coverage_start_fn()
757 --coverage->nesting; in coverage_start_fn()
769 coverage.num_entries = 0; in coverage_start()
770 coverage.nesting = 0; in coverage_start()
845 struct coverage_entry *end = coverage.base + coverage.num_entries; in coverage_add()
892 struct coverage_entry *end = coverage.base + coverage.num_entries; in coverage_end()
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| A D | running_tips.rst | 100 Generating code coverage reports under UML
108 This is different from the "normal" way of getting coverage information that is
124 # Append coverage options to the current config
127 # Extract the coverage information from the build dir (.kunit/)
128 $ lcov -t "my_kunit_tests" -o coverage.info -c -d .kunit/
132 $ genhtml -o /tmp/coverage_html coverage.info
140 $ lcov -t "my_kunit_tests" -o coverage.info -c -d .kunit/ --gcov-tool=/usr/bin/gcov-6
251 Generating code coverage reports
257 your tests as modules. That way you can isolate the coverage from tests from
262 # Reset coverage counters before running the test.
|
| /linux/tools/perf/util/ |
| A D | block-range.c | 177 .coverage = entry->coverage, in block_range__create()
215 .coverage = entry->coverage, in block_range__create()
330 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
|
| A D | block-range.h | 32 u64 coverage; member
|
| /linux/scripts/ |
| A D | Makefile.kcov | 2 kcov-flags-$(CONFIG_CC_HAS_SANCOV_TRACE_PC) += -fsanitize-coverage=trace-pc
3 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp
|
| /linux/Documentation/translations/zh_CN/dev-tools/ |
| A D | gcov.rst | 29 .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
96 在gcc编译时如果配置了选项 ``-ftest-coverage`` 时生成的。
160 /tmp/coverage: 从测试机器上面拷贝的数据文件路径
163 [user@build] gcov -o /tmp/coverage/tmp/out/init main.c
|
| /linux/drivers/of/ |
| A D | Kconfig | 11 compile-coverage.
63 can enable it manually to improve device tree unit test coverage.
88 enable it manually to improve device tree unit test coverage.
|
| /linux/arch/x86/um/vdso/ |
| A D | Makefile | 53 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
54 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-coverage
|
| /linux/arch/um/ |
| A D | Makefile-skas | 7 GCOV_OPT += -fprofile-arcs -ftest-coverage
|
| A D | Kconfig.debug | 22 This option allows developers to retrieve coverage data from a UML
|
| /linux/tools/testing/selftests/arm64/fp/ |
| A D | TODO | 2 - More coverage for ptrace:
|
| A D | README | 61 to maximise test coverage.
96 maximise test coverage.
|
| /linux/drivers/scsi/lpfc/ |
| A D | Makefile | 24 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
|
| /linux/Documentation/features/debug/kcov/ |
| A D | arch-support.txt | 4 # description: arch supports kcov for coverage-guided fuzzing
|
| /linux/Documentation/features/debug/gcov-profile-all/ |
| A D | arch-support.txt | 4 # description: arch supports whole-kernel GCOV code coverage profiling
|
| /linux/arch/um/scripts/ |
| A D | Makefile.rules | 26 $(patsubst -pg,,$(patsubst -fprofile-arcs -ftest-coverage,,$(1)))
|
| /linux/scripts/gcc-plugins/ |
| A D | Kconfig | 29 gcc-4.5 on). It is based on the commit "Add fuzzing coverage support"
79 depends on !COMPILE_TEST # do not reduce test coverage
|
| /linux/arch/arm/boot/dts/ |
| A D | s3c6400.dtsi | 12 * S3C6400 SoC. As device tree coverage for S3C6400 increases, additional
|
| A D | s3c6410.dtsi | 12 * S3C6410 SoC. As device tree coverage for S3C6410 increases, additional
|
| /linux/drivers/net/usb/ |
| A D | sierra_net.c | 127 u8 coverage; member
402 if (lsi->coverage == SIERRA_NET_COVERAGE_NONE || in sierra_net_parse_lsi()
403 lsi->coverage == SIERRA_NET_COVERAGE_NOPACKET) { in sierra_net_parse_lsi()
404 netdev_err(dev->net, "No coverage, 0x%02x\n", lsi->coverage); in sierra_net_parse_lsi()
|