1menu "GCOV-based kernel profiling"
 2
 3config GCOV_KERNEL
 4	bool "Enable gcov-based kernel profiling"
 5	depends on DEBUG_FS
 6	select CONSTRUCTORS if !UML
 
 7	default n
 8	---help---
 9	This option enables gcov-based code profiling (e.g. for code coverage
10	measurements).
11
12	If unsure, say N.
13
14	Additionally specify CONFIG_GCOV_PROFILE_ALL=y to get profiling data
15	for the entire kernel. To enable profiling for specific files or
16	directories, add a line similar to the following to the respective
17	Makefile:
18
19	For a single file (e.g. main.o):
20	        GCOV_PROFILE_main.o := y
21
22	For all files in one directory:
23	        GCOV_PROFILE := y
24
25	To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL
26	is specified, use:
27
28	        GCOV_PROFILE_main.o := n
29	and:
30	        GCOV_PROFILE := n
31
32	Note that the debugfs filesystem has to be mounted to access
33	profiling data.
34
 
 
 
35config GCOV_PROFILE_ALL
36	bool "Profile entire Kernel"
 
37	depends on GCOV_KERNEL
38	depends on SUPERH || S390 || X86 || PPC || MICROBLAZE
39	default n
40	---help---
41	This options activates profiling for the entire kernel.
42
43	If unsure, say N.
44
45	Note that a kernel compiled with profiling flags will be significantly
46	larger and run slower. Also be sure to exclude files from profiling
47	which are not linked to the kernel image to prevent linker errors.
48
49choice
50	prompt "Specify GCOV format"
51	depends on GCOV_KERNEL
52	default GCOV_FORMAT_AUTODETECT
53	---help---
54	The gcov format is usually determined by the GCC version, but there are
55	exceptions where format changes are integrated in lower-version GCCs.
56	In such a case use this option to adjust the format used in the kernel
57	accordingly.
58
59	If unsure, choose "Autodetect".
60
61config GCOV_FORMAT_AUTODETECT
62	bool "Autodetect"
63	---help---
64	Select this option to use the format that corresponds to your GCC
65	version.
66
67config GCOV_FORMAT_3_4
68	bool "GCC 3.4 format"
69	---help---
70	Select this option to use the format defined by GCC 3.4.
71
72config GCOV_FORMAT_4_7
73	bool "GCC 4.7 format"
74	---help---
75	Select this option to use the format defined by GCC 4.7.
76
77endchoice
78
79endmenu

 1# SPDX-License-Identifier: GPL-2.0-only
 2menu "GCOV-based kernel profiling"
 3
 4config GCOV_KERNEL
 5	bool "Enable gcov-based kernel profiling"
 6	depends on DEBUG_FS
 7	depends on !ARCH_WANTS_NO_INSTR || CC_HAS_NO_PROFILE_FN_ATTR
 8	select CONSTRUCTORS
 9	default n
10	help
11	This option enables gcov-based code profiling (e.g. for code coverage
12	measurements).
13
14	If unsure, say N.
15
16	Additionally specify CONFIG_GCOV_PROFILE_ALL=y to get profiling data
17	for the entire kernel. To enable profiling for specific files or
18	directories, add a line similar to the following to the respective
19	Makefile:
20
21	For a single file (e.g. main.o):
22	        GCOV_PROFILE_main.o := y
23
24	For all files in one directory:
25	        GCOV_PROFILE := y
26
27	To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL
28	is specified, use:
29
30	        GCOV_PROFILE_main.o := n
31	and:
32	        GCOV_PROFILE := n
33
34	Note that the debugfs filesystem has to be mounted to access
35	profiling data.
36
37config ARCH_HAS_GCOV_PROFILE_ALL
38	def_bool n
39
40config GCOV_PROFILE_ALL
41	bool "Profile entire Kernel"
42	depends on !COMPILE_TEST
43	depends on GCOV_KERNEL
44	depends on ARCH_HAS_GCOV_PROFILE_ALL
45	default n
46	help
47	This options activates profiling for the entire kernel.
48
49	If unsure, say N.
50
51	Note that a kernel compiled with profiling flags will be significantly
52	larger and run slower. Also be sure to exclude files from profiling
53	which are not linked to the kernel image to prevent linker errors.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
54
55endmenu