Home
last modified time | relevance | path

Searched full:coverage (Results 1 – 25 of 379) sorted by relevance

12345678910>>...16

/kernel/linux/linux-6.6/Documentation/dev-tools/
Dkcov.rst1 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 …]
Dgcov.rst4 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.
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
[all …]
Dtesting-overview.rst66 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
/kernel/linux/linux-5.10/Documentation/networking/
Dudplite.rst37 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 …]
Ddccp.rst112 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
/kernel/linux/linux-6.6/Documentation/networking/
Dudplite.rst37 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 …]
Ddccp.rst112 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
/kernel/linux/linux-5.10/Documentation/dev-tools/
Dkcov.rst1 kcov: code coverage for fuzzing
4 kcov exposes kernel code coverage information in a form suitable for coverage-
5 guided fuzzing (randomized testing). Coverage data of a running kernel is
6 exported via the "kcov" debugfs file. Coverage collection is enabled on a task
7 basis, and thus it 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 function of syscall inputs.
11 To achieve this goal it does not collect coverage in soft/hard interrupts
35 Coverage collection
38 The following program demonstrates coverage collection from within a test
[all …]
Dgcov.rst4 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.
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
[all …]
/kernel/linux/linux-6.6/drivers/gpu/drm/ci/xfails/
Dmsm-sc7180-fails.txt11 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
Dmsm-sdm845-fails.txt44 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
/kernel/linux/linux-5.10/include/net/
Dudplite.h11 #define UDPLITE_SEND_CSCOV 10 /* sender partial coverage (as sent) */
12 #define UDPLITE_RECV_CSCOV 11 /* receiver partial coverage (threshold ) */
44 if (cscov == 0) /* Indicates that full coverage is required. */ in udplite_checksum_init()
48 * Coverage length violates RFC 3828: log and discard silently. in udplite_checksum_init()
50 net_dbg_ratelimited("UDPLite: bad csum coverage %d/%d\n", in udplite_checksum_init()
74 * Sender has set `partial coverage' option on UDP-Lite socket. in udplite_csum_outgoing()
75 * The special case "up->pcslen == 0" signifies full coverage. in udplite_csum_outgoing()
87 * In this case (e.g. last segment), coverage may in udplite_csum_outgoing()
89 * Since packets with coverage length > packet length are in udplite_csum_outgoing()
/kernel/linux/linux-6.6/include/net/
Dudplite.h12 #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()
/kernel/linux/linux-5.10/kernel/
Dkcov.c50 * - task with enabled coverage (we can't unwire it from another task)
51 * - each code section for remote coverage collection
59 /* Coverage buffer shared with user space. */
61 /* Task for which we collect coverage, or NULL. */
63 /* Collecting coverage from remote (background) threads. */
159 * We are interested in code coverage as a function of a syscall inputs, in check_kcov_mode()
161 * coverage collection section in a softirq. in check_kcov_mode()
433 * shouldn't be exiting when it's in a kcov coverage collection in kcov_task_exit()
435 * coverage, and t->kcov->t points to the thread that created the in kcov_task_exit()
591 * Enable coverage for the current task. in kcov_ioctl_locked()
[all …]
/kernel/linux/linux-5.10/tools/perf/util/
Dblock-range.c177 .coverage = entry->coverage, in block_range__create()
215 .coverage = entry->coverage, in block_range__create()
305 * Compute coverage as:
307 * br->coverage / br->sym->max_coverage
312 * Returns [0-1] for coverage and -1 if we had no data what so ever or the
330 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
/kernel/linux/linux-6.6/tools/perf/util/
Dblock-range.c173 .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
326 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
/kernel/linux/linux-6.6/kernel/
Dkcov.c51 * - task with enabled coverage (we can't unwire it from another task)
52 * - each code section for remote coverage collection
60 /* Coverage buffer shared with user space. */
62 /* Task for which we collect coverage, or NULL. */
64 /* Collecting coverage from remote (background) threads. */
178 * We are interested in code coverage as a function of a syscall inputs, in check_kcov_mode()
180 * coverage collection section in a softirq. in check_kcov_mode()
463 * shouldn't be exiting when it's in a kcov coverage collection in kcov_task_exit()
465 * coverage, and t->kcov->t points to the thread that created the in kcov_task_exit()
596 * Enable coverage for the current task. in kcov_ioctl_locked()
[all …]
/kernel/linux/linux-6.6/arch/arm/probes/kprobes/
Dtest-core.c670 * 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 …]
/kernel/linux/linux-5.10/arch/arm/probes/kprobes/
Dtest-core.c670 * 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 …]
/kernel/linux/linux-6.6/Documentation/dev-tools/kunit/
Drunning_tips.rst100 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.
/kernel/linux/linux-5.10/drivers/of/
DKconfig11 compile-coverage.
63 can enable it manually to improve device tree unit test coverage.
94 enable it manually to improve device tree unit test coverage.
/kernel/linux/linux-6.6/drivers/of/
DKconfig11 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.
/kernel/linux/linux-5.10/include/linux/
Dcompiler-clang.h66 * with no_sanitize("coverage"). Prior versions of Clang support coverage
70 #define __no_sanitize_coverage __attribute__((no_sanitize("coverage")))
/kernel/linux/linux-5.10/scripts/
DMakefile.kcov2 kcov-flags-$(CONFIG_CC_HAS_SANCOV_TRACE_PC) += -fsanitize-coverage=trace-pc
3 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp
/kernel/linux/linux-6.6/scripts/
DMakefile.kcov2 kcov-flags-$(CONFIG_CC_HAS_SANCOV_TRACE_PC) += -fsanitize-coverage=trace-pc
3 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp

12345678910>>...16