| /Linux-v4.19/Documentation/networking/ |
| D | udplite.txt | 33 IPPROTO need to be changed; senders additionally set the checksum coverage
52 using partial checksum coverage and so emulate UDP mode (full coverage).
54 To make use of the partial checksum coverage facilities requires setting a
55 single socket option, which takes an integer specifying the coverage length:
57 * Sender checksum coverage: UDPLITE_SEND_CSCOV
64 sets the checksum coverage length to 20 bytes (12b data + 8b header).
70 * Receiver checksum coverage: UDPLITE_RECV_CSCOV
73 required to enable traffic with partial checksum coverage. Its function is
75 all packets which have a coverage _less_ than this value. For example, if
77 packets with a minimum coverage of 20 are admitted:
[all …]
|
| D | dccp.txt | 108 partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
113 DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
114 range 0..15 are acceptable. The default setting is 0 (full coverage),
115 values between 1..15 indicate partial coverage.
118 of 0 means that all packets with a partial coverage will be discarded.
120 coverage value are also acceptable. The higher the number, the more
121 restrictive this setting (see [RFC 4340, sec. 9.2.1]). Partial coverage
|
| /Linux-v4.19/Documentation/dev-tools/ |
| D | kcov.rst | 1 kcov: code coverage for fuzzing
4 kcov exposes kernel code coverage information in a form suitable for coverage-
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
37 The following program demonstrates coverage collection from within a test
66 /* A single fd descriptor allows coverage collection on a single
80 /* Enable coverage collection on the current thread. */
83 /* Reset coverage from the tail of the ioctl() call. */
[all …]
|
| 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.
26 .. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
41 and to get coverage data for the entire kernel::
91 Global reset file: resets all coverage data to zero when
96 tool. Resets file coverage data to zero when written to.
101 option ``-ftest-coverage``.
109 coverage data for such code by keeping a copy of the data associated
111 Once the module is loaded again, the associated coverage counters are
[all …]
|
| /Linux-v4.19/arch/arm/probes/kprobes/ |
| D | test-core.c | 706 struct coverage_table coverage; variable
739 struct coverage_table *coverage = (struct coverage_table *)args; in coverage_start_fn() local
741 struct coverage_entry *entry = coverage->base + coverage->num_entries; in coverage_start_fn()
743 if (coverage->num_entries == MAX_COVERAGE_ENTRIES - 1) { in coverage_start_fn()
748 ++coverage->num_entries; in coverage_start_fn()
752 entry->nesting = coverage->nesting; in coverage_start_fn()
758 ++coverage->nesting; in coverage_start_fn()
759 ret = table_iter(d->table.table, coverage_start_fn, coverage); in coverage_start_fn()
760 --coverage->nesting; in coverage_start_fn()
769 coverage.base = kmalloc_array(MAX_COVERAGE_ENTRIES, in coverage_start()
[all …]
|
| /Linux-v4.19/scripts/ |
| D | Makefile.kcov | 3 kcov-flags-$(CONFIG_CC_HAS_SANCOV_TRACE_PC) += -fsanitize-coverage=trace-pc
4 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp
|
| /Linux-v4.19/tools/perf/util/ |
| D | block-range.c | 175 .coverage = entry->coverage, in block_range__create()
213 .coverage = entry->coverage, in block_range__create()
328 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
|
| D | block-range.h | 28 u64 coverage; member
|
| /Linux-v4.19/drivers/of/ |
| D | Kconfig | 11 compile-coverage.
62 can enable it manually to improve device tree unit test coverage.
101 enable it manually to improve device tree unit test coverage.
|
| /Linux-v4.19/arch/x86/um/vdso/ |
| D | Makefile | 53 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
54 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-coverage
|
| /Linux-v4.19/arch/um/ |
| D | Makefile-skas | 7 GCOV_OPT += -fprofile-arcs -ftest-coverage
|
| D | Kconfig.debug | 20 This option allows developers to retrieve coverage data from a UML
|
| /Linux-v4.19/drivers/scsi/lpfc/ |
| D | Makefile | 24 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
|
| /Linux-v4.19/Documentation/features/debug/gcov-profile-all/ |
| D | arch-support.txt | 4 # description: arch supports whole-kernel GCOV code coverage profiling
|
| /Linux-v4.19/arch/um/scripts/ |
| D | Makefile.rules | 26 $(patsubst -pg,,$(patsubst -fprofile-arcs -ftest-coverage,,$(1)))
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | s3c6400.dtsi | 12 * S3C6400 SoC. As device tree coverage for S3C6400 increases, additional
|
| D | s3c6410.dtsi | 12 * S3C6410 SoC. As device tree coverage for S3C6410 increases, additional
|
| D | s3c64xx.dtsi | 12 * S3C64xx SoCs. As device tree coverage for S3C64xx increases, additional
|
| D | exynos4210.dtsi | 15 * Exynos4210 SoC. As device tree coverage for Exynos4210 increases, additional
|
| /Linux-v4.19/drivers/net/usb/ |
| D | sierra_net.c | 139 u8 coverage; member
419 if (lsi->coverage == SIERRA_NET_COVERAGE_NONE || in sierra_net_parse_lsi()
420 lsi->coverage == SIERRA_NET_COVERAGE_NOPACKET) { in sierra_net_parse_lsi()
421 netdev_err(dev->net, "No coverage, 0x%02x\n", lsi->coverage); in sierra_net_parse_lsi()
|
| /Linux-v4.19/scripts/gcc-plugins/ |
| D | Kconfig | 49 gcc-4.5 on). It is based on the commit "Add fuzzing coverage support"
134 depends on !COMPILE_TEST # do not reduce test coverage
|
| /Linux-v4.19/kernel/gcov/ |
| D | Kconfig | 9 This option enables gcov-based code profiling (e.g. for code coverage
|
| /Linux-v4.19/tools/perf/ |
| D | builtin-annotate.c | 106 entry->coverage++; in process_basic_block()
110 notes->max_coverage = max(notes->max_coverage, entry->coverage); in process_basic_block()
|
| /Linux-v4.19/lib/ |
| D | Kconfig.debug | 745 def_bool $(cc-option,-fsanitize-coverage=trace-pc)
748 bool "Code coverage for fuzzing"
754 KCOV exposes kernel code coverage information in a form suitable
755 for coverage-guided fuzzing (randomized testing).
766 depends on $(cc-option,-fsanitize-coverage=trace-cmp)
771 of fuzzing coverage.
781 filesystem fuzzing with AFL) then you will want to enable coverage
|
| /Linux-v4.19/arch/sh/boards/ |
| D | Kconfig | 23 have sufficient driver coverage to use this option; do not
|
