| /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 | 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 …]
|
| H 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.
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
118 Once the module is loaded again, the associated coverage counters are
[all …]
|
| H A D | testing-devices.rst | 10 with some overlap in coverage and different requirements. This document aims to
45 improve coverage, generate the reference for each platform and enable the exist
|
| H 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/scripts/ |
| 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
|
| 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
|
| /linux/arch/arm/probes/kprobes/ |
| H A 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_objs(struct coverage_entry, in coverage_start()
[all …]
|
| /linux/tools/testing/selftests/net/rds/ |
| H A 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/.
|
| /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()
331 return (double)br->coverage / branch->max_coverage; in block_range__coverage()
|
| /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/Documentation/translations/zh_TW/dev-tools/ |
| H 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/Documentation/translations/zh_CN/dev-tools/ |
| H 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/Documentation/admin-guide/perf/ |
| H A 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.
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/arch/x86/um/vdso/ |
| H A D | Makefile | 47 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
48 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-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/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/drivers/gpu/drm/ci/xfails/ |
| H A D | msm-apq8016-skips.txt | 15 # Currently fails and causes coverage loss for other tests
|
| H A D | meson-g12b-skips.txt | 16 # Currently fails and causes coverage loss for other tests
|
| H A D | rockchip-rk3288-skips.txt | 19 # Currently fails and causes coverage loss for other tests
|
| H A D | panfrost-g12b-skips.txt | 22 # Currently fails and causes coverage loss for other tests
|
| /linux/tools/testing/selftests/arm64/fp/ |
| H A D | TODO | 2 - More coverage for ptrace:
|
| /linux/arch/um/ |
| H A D | Makefile-skas | 11 export UM_GCOV_OPT += -fprofile-arcs -ftest-coverage
|
| /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/drivers/scsi/lpfc/ |
| H A D | Makefile | 24 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
|