Searched full:coverage (Results 1 – 25 of 44) sorted by relevance
12
| /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.
26 .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
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``.
[all …]
|
| 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
|
| /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
|
| /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 …]
|
| D | style.rst | 162 tested, or be under [Kernel Hacking]->[Kernel Testing and Coverage]
|
| /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
|
| /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
|
| /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.
188 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:
|
| /Documentation/features/debug/kcov/ |
| D | arch-support.txt | 4 # description: arch supports kcov for coverage-guided fuzzing
|
| /Documentation/features/debug/gcov-profile-all/ |
| D | arch-support.txt | 4 # description: arch supports whole-kernel GCOV code coverage profiling
|
| /Documentation/devicetree/bindings/usb/ |
| D | microchip,usb5744.yaml | 13 (LS) USB signaling, offering complete coverage of all defined USB operating
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 77 until its completion. This is done deliberately to assist with coverage-guided
|
| /Documentation/rust/ |
| D | testing.rst | 37 Kernel hacking -> Kernel Testing and Coverage -> KUnit - Enable support for unit tests
|
| D | general-information.rst | 80 but it is intended that coverage is expanded as time goes on. "Leaf" modules
|
| /Documentation/gpu/ |
| D | vkms.rst | 131 For all of these, we also want to review the igt test coverage and make sure
|
| D | automated_testing.rst | 122 How to expand coverage
|
| /Documentation/admin-guide/mm/ |
| D | multigen_lru.rst | 131 the coverage as well.
|
| /Documentation/gpu/amdgpu/display/ |
| D | display-contributing.rst | 33 want to pass a large set of tests to increase the test coverage in our CI. If
|
| D | display-manager.rst | 122 * **Coverage**: Blend formula that assumes the pixel color values were not
|
| /Documentation/filesystems/xfs/ |
| D | xfs-maintainer-entry-profile.rst | 64 coverage goals of the project, negotiating with developers to decide
|
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 359 infrastructure is on-going. Initial regular coverage is provided in
361 mount configuration, and includes lockdep and KASAN coverage, see:
|
| /Documentation/process/ |
| D | maintainer-kvm-x86.rst | 274 With one exception, new features *must* come with test coverage. KVM specific
275 tests aren't strictly required, e.g. if coverage is provided by running a
|
| D | botching-up-ioctls.rst | 109 love for signal you'll get an excellent base coverage of all your error
|
12