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 49endmenu 50