| /openbmc/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
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 …]
|
| 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.
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 …]
|
| 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
|
| /openbmc/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 …]
|
| /openbmc/u-boot/tools/patman/ |
| H A D | test_util.py | 20 """Run tests and check that we get 100% coverage
28 exclude_list: List of file patterns to exclude from the coverage
31 required: List of modules which must be in the coverage report
34 ValueError if the code coverage is not 100%
45 cmd = ('PYTHONPATH=$PYTHONPATH:%s/sandbox_spl/tools python-coverage run '
48 stdout = command.Output('python-coverage', 'report')
61 coverage = lines[-1].split(' ')[-1]
63 print coverage
64 if coverage != '100%':
66 print ("Type 'python-coverage html' to get a report in "
[all …]
|
| /openbmc/linux/drivers/gpu/drm/ci/xfails/ |
| H A D | msm-sc7180-fails.txt | 11 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
|
| /openbmc/qemu/python/ |
| H A D | Makefile | 116 .PHONY: check-coverage
117 check-coverage:
118 @coverage run -m avocado --config avocado.cfg run tests/*.py
119 @coverage combine
120 @coverage html
121 @coverage report
132 rm -f .coverage .coverage.*
|
| H A D | .gitignore | 19 # Coverage.py reports
20 .coverage
21 .coverage.*
|
| /openbmc/libpldm/docs/ |
| H A D | fuzzing.md | 70 ## Coverage section in Fuzzing libpldm
72 The coverage provided by a corpus directory can be reported using
73 `tests/fuzz/fuzz-coverage.py`.
77 - Run a binary compiled with `--coverage` against each corpus file
78 - Use [grcov](https://github.com/mozilla/grcov) to aggregate the coverage traces
85 ./tests/fuzz/fuzz-coverage.py fuzzrun/corpus bnoopt/tests/fuzz/fd-fuzz . bnoopt/ coverage-output
|
| /openbmc/u-boot/test/ |
| H A D | run | 49 # This needs you to set up Python test coverage tools.
50 # To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
51 # $ sudo apt-get install python-pytest python-coverage
52 run_test "binman code coverage" ./tools/binman/binman -T
53 run_test "dtoc code coverage" ./tools/dtoc/dtoc -T
54 run_test "fdt code coverage" ./tools/dtoc/test_fdt -T
|
| /openbmc/phosphor-webui/ |
| H A D | karma.conf.js | 15 // Reference: https://github.com/karma-runner/karma-coverage
16 // Output code coverage files
17 'coverage'
39 // Configure code coverage reporter
41 {dir: 'coverage/', reporters: [{type: 'text-summary'}, {type: 'html'}]},
|
| /openbmc/qemu/scripts/coverage/ |
| H A D | compare_gcov_json.py | 7 # - run make coverage-html in each
9 # --print-summary -o coverage.json --root ../../ . *.p
24 description='analyse the differences in coverage between two runs')
64 # if this file has any coverage add it to the system
109 print(f"{b_name} missing coverage in {len(first_missing)} files")
113 print(f"{a_name} missing coverage in {len(second_missing)} files")
|
| /openbmc/openpower-inventory-upload/ |
| H A D | .gitignore | 37 # Unit test / coverage reports
40 .coverage
41 .coverage.*
44 coverage.xml
|
| /openbmc/qemu/scripts/ci/ |
| H A D | coverage-summary.sh | 5 # Summerise the state of code coverage with gcovr and tweak the output
9 # directly. See also "make coverage-report"
14 # first generate the coverage report
26 # and dump, stripping out 0% coverage
|
| /openbmc/linux/include/net/ |
| H A 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()
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | Makefile | 44 @echo " coverage to run coverage check of the documentation (if enabled)"
203 .PHONY: coverage
204 coverage: target
205 $(SPHINXBUILD) -b coverage $(ALLSPHINXOPTS) $(BUILDDIR)/coverage
206 @echo "Testing of coverage in the sources finished, look at the " \
207 "results in $(BUILDDIR)/coverage/python.txt."
|
| /openbmc/pyphosphor/ |
| H A D | .gitignore | 59 # Unit test / coverage reports
62 .coverage
63 .coverage.*
66 coverage.xml
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/suitesparse/suitesparse/ |
| H A D | 0001-Preserve-CXXFLAGS-from-environment-in-Mongoose.patch | 27 SET(CMAKE_CXX_FLAGS_DEBUG "--coverage -g -fwrapv")
28 SET(CMAKE_C_FLAGS_DEBUG "--coverage -g")
29 SET(CMAKE_EXE_LINKER_FLAGS_DEBUG "--coverage -g")
38 SET(CMAKE_EXE_LINKER_FLAGS_DEBUG "-fprofile-arcs -ftest-coverage")
|
| /openbmc/libpldm/tests/fuzz/ |
| H A D | fuzz-coverage.py | 4 # usage: fuzz-coverage.py [-h] corpus program srcdir builddir outdir
7 # built with coverage, and produces a html report.
9 # The program should be built with --coverage -fprofile-abs-path
25 print(f"Removed old coverage {c}", file=sys.stderr)
|
| /openbmc/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
326 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
|
| /openbmc/linux/kernel/ |
| H A D | kcov.c | 51 * - 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 …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/mcelog/mce-test/ |
| H A D | 0001-gcov_merge.py-scov_merge.py-switch-to-python3.patch | 25 # the coverage of several test cases.
70 # Merge mce serverity coverage file from several test cases. This can
71 # be used to check the coverage of several test cases.
99 - print 'Usage: %s <severities coverage files>' % (sys.argv[0])
100 + print('Usage: %s <severities coverage files>' % (sys.argv[0]))
|
| /openbmc/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 …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | fuzzing.rst | 12 fuzzer tracks the code coverage triggered by the input. Based on these
78 coverage table. Useful for targets with "magic" constants. If Arg1 came from
84 better coverage performance, depending on the target.
89 Generating Coverage Reports
92 Code coverage is a crucial metric for evaluating a fuzzer's performance.
94 unique blocks/edges covered. To examine coverage on a line-by-line basis we
95 can use Clang coverage:
107 4. Execute these commands to generate a detailed HTML coverage-report::
116 Coverage over virtual devices can be improved by adding additional fuzzers.
|
| /openbmc/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
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.
|