750358ee4f
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a while now and is almost always enabled by default. As agreed during the Linux kernel summit, remove it from any "depends on" lines in Kconfigs. Cc: WANG Cong <xiyou.wangcong@gmail.com> Signed-off-by: Kees Cook <keescook@chromium.org> Acked-by: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
50 lines
1.3 KiB
Plaintext
50 lines
1.3 KiB
Plaintext
menu "GCOV-based kernel profiling"
|
|
|
|
config GCOV_KERNEL
|
|
bool "Enable gcov-based kernel profiling"
|
|
depends on DEBUG_FS
|
|
select CONSTRUCTORS if !UML
|
|
default n
|
|
---help---
|
|
This option enables gcov-based code profiling (e.g. for code coverage
|
|
measurements).
|
|
|
|
If unsure, say N.
|
|
|
|
Additionally specify CONFIG_GCOV_PROFILE_ALL=y to get profiling data
|
|
for the entire kernel. To enable profiling for specific files or
|
|
directories, add a line similar to the following to the respective
|
|
Makefile:
|
|
|
|
For a single file (e.g. main.o):
|
|
GCOV_PROFILE_main.o := y
|
|
|
|
For all files in one directory:
|
|
GCOV_PROFILE := y
|
|
|
|
To exclude files from being profiled even when CONFIG_GCOV_PROFILE_ALL
|
|
is specified, use:
|
|
|
|
GCOV_PROFILE_main.o := n
|
|
and:
|
|
GCOV_PROFILE := n
|
|
|
|
Note that the debugfs filesystem has to be mounted to access
|
|
profiling data.
|
|
|
|
config GCOV_PROFILE_ALL
|
|
bool "Profile entire Kernel"
|
|
depends on GCOV_KERNEL
|
|
depends on SUPERH || S390 || X86 || PPC || MICROBLAZE
|
|
default n
|
|
---help---
|
|
This options activates profiling for the entire kernel.
|
|
|
|
If unsure, say N.
|
|
|
|
Note that a kernel compiled with profiling flags will be significantly
|
|
larger and run slower. Also be sure to exclude files from profiling
|
|
which are not linked to the kernel image to prevent linker errors.
|
|
|
|
endmenu
|