| /Linux-v6.6/Documentation/dev-tools/ |
| D | kcov.rst | 1 KCOV: code coverage for fuzzing
4 KCOV collects and exposes kernel code coverage information in a form suitable
5 for coverage-guided fuzzing. Coverage data of a running kernel is exported via
7 thus KCOV can capture precise coverage of a single system call.
9 Note that KCOV does not aim to collect as much coverage as possible. It aims
10 to collect more or less stable coverage that is a function of syscall inputs.
11 To achieve this goal, it does not collect coverage in soft/hard interrupts
12 (unless remove coverage collection is enabled, see below) and from some
15 Besides collecting code coverage, KCOV can also collect comparison operands.
18 Besides collecting coverage data from syscall handlers, KCOV can also collect
[all …]
|
| 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``.
105 coverage data for such code by keeping a copy of the data associated
107 Once the module is loaded again, the associated coverage counters are
[all …]
|
| 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-v6.6/Documentation/networking/ |
| D | udplite.rst | 37 IPPROTO need to be changed; senders additionally set the checksum coverage
58 using partial checksum coverage and so emulate UDP mode (full coverage).
60 To make use of the partial checksum coverage facilities requires setting a
61 single socket option, which takes an integer specifying the coverage length:
63 * Sender checksum coverage: UDPLITE_SEND_CSCOV
70 sets the checksum coverage length to 20 bytes (12b data + 8b header).
76 * Receiver checksum coverage: UDPLITE_RECV_CSCOV
79 required to enable traffic with partial checksum coverage. Its function is
81 all packets which have a coverage _less_ than this value. For example, if
83 packets with a minimum coverage of 20 are admitted::
[all …]
|
| 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-v6.6/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-fails.txt | 11 kms_plane_alpha_blend@coverage-7efc,Fail
12 kms_plane_alpha_blend@coverage-vs-premult-vs-constant,Fail
14 kms_plane_alpha_blend@pipe-A-coverage-7efc,Fail
15 kms_plane_alpha_blend@pipe-A-coverage-vs-premult-vs-constant,Fail
21 kms_plane_alpha_blend@pipe-B-coverage-7efc,Fail
22 kms_plane_alpha_blend@pipe-B-coverage-vs-premult-vs-constant,Fail
|
| D | msm-sdm845-fails.txt | 44 kms_plane_alpha_blend@coverage-7efc,Fail
45 kms_plane_alpha_blend@coverage-vs-premult-vs-constant,Fail
47 kms_plane_alpha_blend@pipe-A-coverage-7efc,Fail
48 kms_plane_alpha_blend@pipe-A-coverage-vs-premult-vs-constant,Fail
|
| /Linux-v6.6/arch/arm/probes/kprobes/ |
| D | test-core.c | 703 struct coverage_table coverage; variable
736 struct coverage_table *coverage = (struct coverage_table *)args; in coverage_start_fn() local
738 struct coverage_entry *entry = coverage->base + coverage->num_entries; in coverage_start_fn()
740 if (coverage->num_entries == MAX_COVERAGE_ENTRIES - 1) { 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()
756 ret = table_iter(d->table.table, coverage_start_fn, coverage); in coverage_start_fn()
757 --coverage->nesting; in coverage_start_fn()
766 coverage.base = kmalloc_array(MAX_COVERAGE_ENTRIES, in coverage_start()
[all …]
|
| /Linux-v6.6/scripts/ |
| 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-v6.6/tools/perf/util/ |
| D | block-range.c | 173 .coverage = entry->coverage, in block_range__create()
211 .coverage = entry->coverage, in block_range__create()
326 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
|
| D | block-range.h | 32 u64 coverage; member
|
| /Linux-v6.6/Documentation/translations/zh_CN/dev-tools/ |
| 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-v6.6/Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 34 traffic coverage.
66 the PMU traffic coverage.
96 the PMU traffic coverage.
125 for more info about the PMU traffic coverage.
165 for more info about the PMU traffic coverage.
191 The PMU traffic coverage may vary dependent on the chip configuration:
222 | Following table contains traffic coverage of Grace SoC PMU in socket-A:
279 | Following table contains traffic coverage of Grace SoC PMU in socket-A:
|
| /Linux-v6.6/Documentation/dev-tools/kunit/ |
| 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
125 # 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-v6.6/arch/x86/um/vdso/ |
| D | Makefile | 56 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
57 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-coverage
|
| /Linux-v6.6/drivers/of/ |
| D | Kconfig | 11 compile-coverage.
75 can enable it manually to improve device tree unit test coverage.
100 enable it manually to improve device tree unit test coverage.
|
| /Linux-v6.6/arch/um/ |
| D | Makefile-skas | 7 GCOV_OPT += -fprofile-arcs -ftest-coverage
|
| /Linux-v6.6/tools/testing/selftests/arm64/fp/ |
| D | TODO | 2 - More coverage for ptrace:
|
| /Linux-v6.6/tools/testing/kunit/configs/ |
| D | coverage_uml.config | 1 # This config fragment enables coverage on UML, which is different from the
|
| /Linux-v6.6/drivers/scsi/lpfc/ |
| D | Makefile | 24 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
|
| /Linux-v6.6/Documentation/features/debug/kcov/ |
| D | arch-support.txt | 4 # description: arch supports kcov for coverage-guided fuzzing
|
| /Linux-v6.6/Documentation/features/debug/gcov-profile-all/ |
| D | arch-support.txt | 4 # description: arch supports whole-kernel GCOV code coverage profiling
|
| /Linux-v6.6/tools/perf/tests/config-fragments/ |
| D | README | 2 defconfig to give full test coverage of a perf test run. This is only
|
| /Linux-v6.6/arch/um/scripts/ |
| D | Makefile.rules | 26 $(patsubst -pg,,$(patsubst -fprofile-arcs -ftest-coverage,,$(1)))
|
| /Linux-v6.6/arch/arm/boot/dts/samsung/ |
| D | s3c6400.dtsi | 12 * S3C6400 SoC. As device tree coverage for S3C6400 increases, additional
|
