| /linux-6.14.4/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
6 the ``kcov`` debugfs file. Coverage collection is enabled on a task basis, and
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.
[all …]
|
| D | gcov.rst | 4 gcov profiling kernel support enables the use of GCC's coverage testing
5 tool gcov_ with the Linux kernel. Coverage data of a running kernel
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.
37 and to get coverage data for the entire kernel::
86 generate coverage reports. If left unset the report is omitted.
98 Global reset file: resets all coverage data to zero when
103 tool. Resets file coverage data to zero when written to.
108 option ``-ftest-coverage``.
116 coverage data for such code by keeping a copy of the data associated
[all …]
|
| D | testing-devices.rst | 10 with some overlap in coverage and different requirements. This document aims to
20 * **Coverage**: Probe status for devices described in Devicetree
25 * **Coverage**: Error (or more critical) log messages presence coming from any
31 * **Coverage**: Presence and probe status of USB or PCI devices that have been
39 * **Coverage**: Presence of all devices
45 improve coverage, generate the reference for each platform and enable the exist
|
| D | testing-overview.rst | 66 Code Coverage Tools
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-6.14.4/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-6.14.4/include/linux/ |
| D | kcov.h | 13 /* Coverage collection is not enabled yet. */
18 * Tracing coverage collection mode.
60 * workaround for KCOV's lack of nested remote coverage sections support.
66 * 1. Only collects coverage when called in the softirq context. This allows
67 * avoiding nested remote coverage collection sections in the task context.
69 * within an existing remote coverage collection section. Thus, KCOV should
70 * not attempt to start collecting coverage within the coverage collection
73 * 2. Disables interrupts for the duration of the coverage collection section.
74 * This allows avoiding nested remote coverage collection sections in the
79 * the middle of its remote coverage collection section, and the interrupt
|
| D | compiler-clang.h | 83 * with no_sanitize("coverage"). Prior versions of Clang support coverage
87 #define __no_sanitize_coverage __attribute__((no_sanitize("coverage")))
|
| /linux-6.14.4/include/net/ |
| D | udplite.h | 12 #define UDPLITE_SEND_CSCOV 10 /* sender partial coverage (as sent) */
13 #define UDPLITE_RECV_CSCOV 11 /* receiver partial coverage (threshold ) */
45 if (cscov == 0) /* Indicates that full coverage is required. */ in udplite_checksum_init()
49 * Coverage length violates RFC 3828: log and discard silently. in udplite_checksum_init()
51 net_dbg_ratelimited("UDPLite: bad csum coverage %d/%d\n", in udplite_checksum_init()
|
| /linux-6.14.4/kernel/ |
| D | kcov.c | 52 * - task with enabled coverage (we can't unwire it from another task)
53 * - each code section for remote coverage collection
61 /* Coverage buffer shared with user space. */
63 /* Task for which we collect coverage, or NULL. */
65 /* Collecting coverage from remote (background) threads. */
179 * We are interested in code coverage as a function of a syscall inputs, in check_kcov_mode()
181 * coverage collection section in a softirq. in check_kcov_mode()
464 * shouldn't be exiting when it's in a kcov coverage collection in kcov_task_exit()
466 * coverage, and t->kcov->t points to the thread that created the in kcov_task_exit()
597 * Enable coverage for the current task. in kcov_ioctl_locked()
[all …]
|
| /linux-6.14.4/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
146 # Build with LLVM and append coverage options to the current config
149 $ llvm-cov export --format=lcov .kunit/vmlinux -instr-profile default.profdata > coverage.info
150 …# The coverage.info file is in lcov-compatible format and it can be used to e.g. generate HTML rep…
[all …]
|
| /linux-6.14.4/tools/testing/selftests/net/rds/ |
| D | README.txt | 4 These scripts provide a coverage test for RDS-TCP by creating two
11 kernel may optionally be configured to omit the coverage report as well.
41 An HTML coverage report will be output in tools/testing/selftests/net/rds/rds_logs/coverage/.
|
| D | run.sh | 67 # Check to see if the kconfig has the required configs to generate a coverage report
71 echo "INFO: CONFIG_GCOV_PROFILE_RDS should be enabled for coverage reports"
75 echo "INFO: CONFIG_GCOV_KERNEL should be enabled for coverage reports"
79 echo "INFO: CONFIG_GCOV_PROFILE_ALL should be disabled for coverage reports"
189 COVR_DIR="${LOG_DIR}/coverage/"
204 echo saving coverage data...
215 echo "Coverage report will be skipped"
|
| /linux-6.14.4/tools/perf/util/ |
| D | block-range.c | 173 .coverage = entry->coverage, in block_range__create()
211 .coverage = entry->coverage, in block_range__create()
301 * Compute coverage as:
303 * br->coverage / br->sym->max_coverage
308 * Returns [0-1] for coverage and -1 if we had no data what so ever or the
331 return (double)br->coverage / branch->max_coverage; in block_range__coverage()
|
| /linux-6.14.4/arch/arm/probes/kprobes/ |
| D | test-core.c | 670 * Decoding table test coverage analysis
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()
741 pr_err("FAIL: Out of space for test coverage data"); 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()
[all …]
|
| /linux-6.14.4/scripts/ |
| D | Makefile.compiler | 75 …LAGS += $(call __rustc-option,$(RUSTC),$(MY_RUSTFLAGS),-Cinstrument-coverage,-Zinstrument-coverage)
83 # Usage: rustflags-y += $(call rustc-option,-Cinstrument-coverage,-Zinstrument-coverage)
88 # Usage: flag := $(call rustc-option-yn,-Cinstrument-coverage)
|
| 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-6.14.4/drivers/of/ |
| D | Kconfig | 17 compile-coverage.
89 can enable it manually to improve device tree unit test coverage.
114 enable it manually to improve device tree unit test coverage.
|
| /linux-6.14.4/Documentation/translations/zh_TW/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-6.14.4/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-6.14.4/Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 34 traffic coverage.
66 the PMU traffic coverage.
112 the PMU traffic coverage.
157 for more info about the PMU traffic coverage.
198 for more info about the PMU traffic coverage.
222 Traffic Coverage
225 The PMU traffic coverage may vary dependent on the chip configuration:
256 | Following table contains traffic coverage of Grace SoC PMU in socket-A:
313 | Following table contains traffic coverage of Grace SoC PMU in socket-A:
|
| /linux-6.14.4/drivers/gpu/drm/ci/xfails/ |
| D | msm-sc7180-trogdor-kingoftown-fails.txt | 16 kms_plane_alpha_blend@coverage-7efc,Fail
17 kms_plane_alpha_blend@coverage-vs-premult-vs-constant,Fail
|
| D | msm-sc7180-trogdor-lazor-limozeen-fails.txt | 16 kms_plane_alpha_blend@coverage-7efc,Fail
17 kms_plane_alpha_blend@coverage-vs-premult-vs-constant,Fail
|
| D | msm-sdm845-fails.txt | 27 kms_plane_alpha_blend@coverage-7efc,Fail
28 kms_plane_alpha_blend@coverage-vs-premult-vs-constant,Fail
|
| /linux-6.14.4/lib/ |
| D | test_linear_ranges.c | 19 * coverage" - measured as line coverage. And that is one of the worst things
22 * Ask people to provide line coverage and they do. I've seen clever tools
30 * Especially if you were are asked to proivde 100% line-coverage x_x. So what
|