Home
last modified time | relevance | path

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

/linux-4.4.14/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-4.4.14/Documentation/
Dgcov.txt18 gcov profiling kernel support enables the use of GCC's coverage testing
21 To get coverage data for a specific file, change to the kernel build
30 for the entire kernel and provide coverage overviews in HTML format.
42 [2] http://ltp.sourceforge.net/coverage/lcov.php
57 and to get coverage data for the entire kernel:
103 Global reset file: resets all coverage data to zero when
108 tool. Resets file coverage data to zero when written to.
113 option -ftest-coverage.
121 coverage data for such code by keeping a copy of the data associated
123 Once the module is loaded again, the associated coverage counters are
[all …]
D00-INDEX201 - use of GCC's coverage testing tool "gcov" with the Linux kernel
/linux-4.4.14/arch/arm/probes/kprobes/
Dtest-core.c762 struct coverage_table coverage; variable
795 struct coverage_table *coverage = (struct coverage_table *)args; in coverage_start_fn() local
797 struct coverage_entry *entry = coverage->base + coverage->num_entries; in coverage_start_fn()
799 if (coverage->num_entries == MAX_COVERAGE_ENTRIES - 1) { in coverage_start_fn()
804 ++coverage->num_entries; in coverage_start_fn()
808 entry->nesting = coverage->nesting; in coverage_start_fn()
814 ++coverage->nesting; in coverage_start_fn()
815 ret = table_iter(d->table.table, coverage_start_fn, coverage); in coverage_start_fn()
816 --coverage->nesting; in coverage_start_fn()
825 coverage.base = kmalloc(MAX_COVERAGE_ENTRIES * in coverage_start()
[all …]
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
Dnv50.c35 u32 coverage = 0; in nv50_vm_map_pgt() local
40 coverage = (nvkm_memory_size(pgt[0]) >> 3) << 12; in nv50_vm_map_pgt()
45 coverage = (nvkm_memory_size(pgt[1]) >> 3) << 16; in nv50_vm_map_pgt()
49 if (coverage <= 32 * 1024 * 1024) in nv50_vm_map_pgt()
51 else if (coverage <= 64 * 1024 * 1024) in nv50_vm_map_pgt()
53 else if (coverage <= 128 * 1024 * 1024) in nv50_vm_map_pgt()
/linux-4.4.14/drivers/of/
DKconfig10 compile-coverage.
56 can enable it manually to improve device tree unit test coverage.
113 enable it manually to improve device tree unit test coverage.
/linux-4.4.14/arch/x86/um/vdso/
DMakefile49 CFLAGS_REMOVE_vdso-note.o = -pg -fprofile-arcs -ftest-coverage
50 CFLAGS_REMOVE_um_vdso.o = -pg -fprofile-arcs -ftest-coverage
/linux-4.4.14/arch/um/
DMakefile-skas7 GCOV_OPT += -fprofile-arcs -ftest-coverage
DKconfig.debug22 This option allows developers to retrieve coverage data from a UML
/linux-4.4.14/drivers/scsi/lpfc/
DMakefile22 ccflags-$(GCOV) := -fprofile-arcs -ftest-coverage
/linux-4.4.14/arch/um/scripts/
DMakefile.rules25 $(patsubst -pg,,$(patsubst -fprofile-arcs -ftest-coverage,,$(1)))
/linux-4.4.14/Documentation/features/debug/gcov-profile-all/
Darch-support.txt4 # description: arch supports whole-kernel GCOV code coverage profiling
/linux-4.4.14/arch/arm/boot/dts/
Ds3c6400.dtsi11 * S3C6400 SoC. As device tree coverage for S3C6400 increases, additional
Ds3c6410.dtsi11 * S3C6410 SoC. As device tree coverage for S3C6410 increases, additional
Dexynos4212.dtsi12 * Exynos4212 SoC. As device tree coverage for Exynos4212 increases, additional
Dexynos4412.dtsi12 * Exynos4412 SoC. As device tree coverage for Exynos4412 increases, additional
Ds3c64xx.dtsi11 * S3C64xx SoCs. As device tree coverage for S3C64xx increases, additional
Dexynos4210.dtsi14 * Exynos4210 SoC. As device tree coverage for Exynos4210 increases, additional
Dexynos4x12.dtsi12 * Exynos4x12 SoC. As device tree coverage for Exynos4x12 increases, additional
Dexynos3250.dtsi12 * Exynos3250 SoC. As device tree coverage for Exynos3250 increases, additional
Ds5pv210.dtsi14 * S5PV210 SoC. As device tree coverage for S5PV210 increases, additional
Dexynos4415.dtsi11 * Exynos4415 SoC. As device tree coverage for Exynos4415 increases, additional
Ds5pv210-pinctrl.dtsi14 * S5PV210 SoC. As device tree coverage for S5PV210 increases, additional
Dexynos4.dtsi14 * Exynos4 SoCs. As device tree coverage for Exynos4 increases, additional
Dexynos5250.dtsi12 * EXYNOS5250 SoC. As device tree coverage for EXYNOS5250 increases,
/linux-4.4.14/drivers/net/usb/
Dsierra_net.c139 u8 coverage; member
383 if (lsi->coverage == SIERRA_NET_COVERAGE_NONE in sierra_net_parse_lsi()
384 || lsi->coverage == SIERRA_NET_COVERAGE_NOPACKET) { in sierra_net_parse_lsi()
385 netdev_err(dev->net, "No coverage, 0x%02x\n", lsi->coverage); in sierra_net_parse_lsi()
/linux-4.4.14/kernel/gcov/
DKconfig9 This option enables gcov-based code profiling (e.g. for code coverage
/linux-4.4.14/arch/frv/mm/
Dtlb-miss.S612 # map this PTD instead and record coverage address
/linux-4.4.14/Documentation/frv/
Dmmu-layout.txt179 coverage of the cached item is greater.
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt103 love for signal you'll get an excellent base coverage of all your error
/linux-4.4.14/Documentation/RCU/
Dtorture.txt53 gives best overall test coverage.
/linux-4.4.14/Documentation/development-process/
D1.Intro217 be required to provide reasonably comprehensive coverage, and your users
/linux-4.4.14/
DMakefile367 CFLAGS_GCOV = -fprofile-arcs -ftest-coverage -fno-tree-loop-im
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt193 4. You can run gprof (profiling) and gcov (coverage testing).