Home
last modified time | relevance | path

Searched refs:coverage (Results 1 – 25 of 50) sorted by relevance

12

/Linux-v5.4/Documentation/networking/
Dudplite.txt33 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 …]
Ddccp.txt108 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-v5.4/Documentation/dev-tools/
Dkcov.rst1 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 …]
Dgcov.rst4 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
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
107 Once the module is loaded again, the associated coverage counters are
[all …]
/Linux-v5.4/arch/arm/probes/kprobes/
Dtest-core.c703 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_array(MAX_COVERAGE_ENTRIES, in coverage_start()
[all …]
/Linux-v5.4/scripts/
DMakefile.kcov4 kcov-flags-$(CONFIG_CC_HAS_SANCOV_TRACE_PC) += -fsanitize-coverage=trace-pc
5 kcov-flags-$(CONFIG_KCOV_ENABLE_COMPARISONS) += -fsanitize-coverage=trace-cmp
/Linux-v5.4/tools/perf/util/
Dblock-range.c177 .coverage = entry->coverage, in block_range__create()
215 .coverage = entry->coverage, in block_range__create()
330 return (double)br->coverage / symbol__annotation(sym)->max_coverage; in block_range__coverage()
Dblock-range.h32 u64 coverage; member
Dannotate.c1319 p = 100 *(double)br->entry / branch->coverage; in annotate__branch_printf()
1336 double p = 100*(double)br->taken / br->coverage; in annotate__branch_printf()
2794 double ipc = 0.0, coverage = 0.0; in ipc_coverage_string() local
2800 coverage = notes->cover_insn * 100.0 / in ipc_coverage_string()
2805 ipc, coverage); in ipc_coverage_string()
/Linux-v5.4/drivers/of/
DKconfig11 compile-coverage.
63 can enable it manually to improve device tree unit test coverage.
101 enable it manually to improve device tree unit test coverage.
/Linux-v5.4/arch/x86/um/vdso/
DMakefile53 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
54 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-coverage
/Linux-v5.4/arch/um/
DMakefile-skas7 GCOV_OPT += -fprofile-arcs -ftest-coverage
DKconfig.debug21 This option allows developers to retrieve coverage data from a UML
/Linux-v5.4/drivers/scsi/lpfc/
DMakefile24 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
/Linux-v5.4/Documentation/features/debug/gcov-profile-all/
Darch-support.txt4 # description: arch supports whole-kernel GCOV code coverage profiling
/Linux-v5.4/arch/um/scripts/
DMakefile.rules26 $(patsubst -pg,,$(patsubst -fprofile-arcs -ftest-coverage,,$(1)))
/Linux-v5.4/arch/arm/boot/dts/
Ds3c6400.dtsi12 * S3C6400 SoC. As device tree coverage for S3C6400 increases, additional
Ds3c6410.dtsi12 * S3C6410 SoC. As device tree coverage for S3C6410 increases, additional
Ds3c64xx.dtsi12 * S3C64xx SoCs. As device tree coverage for S3C64xx increases, additional
/Linux-v5.4/scripts/gcc-plugins/
DKconfig52 gcc-4.5 on). It is based on the commit "Add fuzzing coverage support"
104 depends on !COMPILE_TEST # do not reduce test coverage
/Linux-v5.4/drivers/net/usb/
Dsierra_net.c127 u8 coverage; member
407 if (lsi->coverage == SIERRA_NET_COVERAGE_NONE || in sierra_net_parse_lsi()
408 lsi->coverage == SIERRA_NET_COVERAGE_NOPACKET) { in sierra_net_parse_lsi()
409 netdev_err(dev->net, "No coverage, 0x%02x\n", lsi->coverage); in sierra_net_parse_lsi()
/Linux-v5.4/security/
DKconfig.hardening13 such variables, depending on the chosen level of coverage.
33 greatest coverage (since all functions can have their
38 This chooses the level of coverage over classes of potentially
/Linux-v5.4/kernel/gcov/
DKconfig10 This option enables gcov-based code profiling (e.g. for code coverage
/Linux-v5.4/tools/perf/
Dbuiltin-annotate.c111 entry->coverage++; in process_basic_block()
115 notes->max_coverage = max(notes->max_coverage, entry->coverage); in process_basic_block()
/Linux-v5.4/Documentation/gpu/
Dvkms.rst61 For all of these, we also want to review the igt test coverage and make sure all

12