| /linux/Documentation/networking/ |
| H A 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 …]
|
| /linux/Documentation/dev-tools/ |
| H A 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 …]
|
| H A 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/Documentation/dev-tools/kunit/ |
| H 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
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/tools/testing/selftests/net/rds/ |
| H A D | README.txt | 4 These scripts provide a coverage test for RDS-TCP and RDS-RDMA (over
14 configured to omit the coverage report as well.
|
| H A D | run.sh | |
| /linux/tools/perf/util/ |
| H A 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()
|
| H A D | block-range.h | 18 * @coverage: number of blocks that cover this range
32 u64 coverage; member
|
| /linux/arch/arm/probes/kprobes/ |
| H A 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/scripts/ |
| H A D | Makefile.kstack_erase | 12 kstack-erase-cflags-y += -fsanitize-coverage=stack-depth
13 kstack-erase-cflags-y += -fsanitize-coverage-stack-depth-callback-min=$(CONFIG_KSTACK_ERASE_TRACK_M…
14 DISABLE_KSTACK_ERASE := -fno-sanitize-coverage=stack-depth
|
| H A D | Makefile.compiler | 79 …LAGS += $(call __rustc-option,$(RUSTC),$(MY_RUSTFLAGS),-Cinstrument-coverage,-Zinstrument-coverage)
87 # Usage: rustflags-y += $(call rustc-option,-Cinstrument-coverage,-Zinstrument-coverage)
92 # Usage: flag := $(call rustc-option-yn,-Cinstrument-coverage)
|
| H A D | Makefile.kcov | 2 kcov-flags-y += -fsanitize-coverage=trace-pc
3 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp
6 kcov-rflags-y += -Cllvm-args=-sanitizer-coverage-level=3
7 kcov-rflags-y += -Cllvm-args=-sanitizer-coverage-trace-pc
8 kcov-rflags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -Cllvm-args=-sanitizer-coverage-trace-compares
|
| /linux/drivers/of/ |
| H A 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/tools/sched_ext/ |
| H A D | Kconfig | 29 # Enable extra scheduling features (for a better code coverage while testing
36 # Enable fully preemptible kernel for a better test coverage of the schedulers
|
| /linux/include/uapi/linux/ |
| H A D | kcov.h | 13 __u32 area_size; /* Length of coverage buffer in words */
28 * Tracing coverage collection mode.
|
| /linux/security/ |
| H A D | Kconfig.hardening | 29 greatest coverage (since all functions can have their
34 This chooses the level of coverage over classes of potentially
86 def_bool $(cc-option,-fsanitize-coverage-stack-depth-callback-min=1)
124 instrumented. This is useful for comparing coverage between
|
| /linux/tools/testing/selftests/arm64/fp/ |
| H A D | README | 61 to maximise test coverage.
96 maximise test coverage.
|
| H A D | TODO | 2 - More coverage for ptrace:
|
| /linux/tools/perf/tests/config-fragments/ |
| H A D | README | 2 defconfig to give full test coverage of a perf test run. This is only
|
| /linux/tools/testing/kunit/configs/ |
| H A D | coverage_uml.config | 1 # This config fragment enables coverage on UML, which is different from the
|
| /linux/arch/um/ |
| H A D | Makefile-skas | 11 export UM_GCOV_OPT += -fprofile-arcs -ftest-coverage
|
| H A D | Kconfig.debug | 22 This option allows developers to retrieve coverage data from a UML
|
| /linux/drivers/net/usb/ |
| H A D | sierra_net.c | 110 /* LSI Coverage */
125 u8 coverage; member
399 /* Validate the coverage */ in sierra_net_parse_lsi()
400 if (lsi->coverage == SIERRA_NET_COVERAGE_NONE || in sierra_net_parse_lsi()
401 lsi->coverage == SIERRA_NET_COVERAGE_NOPACKET) { in sierra_net_parse_lsi()
402 netdev_err(dev->net, "No coverage, 0x%02x\n", lsi->coverage); in sierra_net_parse_lsi()
|
| /linux/kernel/rcu/ |
| H A D | Makefile | 2 # Any varying coverage in these files is non-deterministic
|
| /linux/net/rds/ |
| H A D | Makefile | 19 # for GCOV coverage profiling
|