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 ARCH_HAS_GCOV_PROFILE_ALL def_bool n config GCOV_PROFILE_ALL bool "Profile entire Kernel" depends on !COMPILE_TEST depends on GCOV_KERNEL depends on ARCH_HAS_GCOV_PROFILE_ALL 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. choice prompt "Specify GCOV format" depends on GCOV_KERNEL default GCOV_FORMAT_AUTODETECT ---help--- The gcov format is usually determined by the GCC version, but there are exceptions where format changes are integrated in lower-version GCCs. In such a case use this option to adjust the format used in the kernel accordingly. If unsure, choose "Autodetect". config GCOV_FORMAT_AUTODETECT bool "Autodetect" ---help--- Select this option to use the format that corresponds to your GCC version. config GCOV_FORMAT_3_4 bool "GCC 3.4 format" ---help--- Select this option to use the format defined by GCC 3.4. config GCOV_FORMAT_4_7 bool "GCC 4.7 format" ---help--- Select this option to use the format defined by GCC 4.7. endchoice endmenu mmitdiff
path: root/drivers/usb/isp1760/Kconfig
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-02-01 12:46:17 -0500
committerDavid S. Miller <davem@davemloft.net>2017-02-01 12:46:17 -0500
commit889711a03e0fba427fb85317900e93c74e3be02a (patch)
tree05af2eda6502a95cf11935cce1e9b25a1340e7ca /drivers/usb/isp1760/Kconfig
parentff1176f6164f3d151ee64c05d3f7b6662a81b982 (diff)
parent7243a1af37a4dc9225004546d9d0756c529ad3ce (diff)
Merge tag 'wireless-drivers-next-for-davem-2017-02-01' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
Kalle Valo says: ==================== wireless-drivers-next patches for 4.11 It's nice to see rt2x00 development has becoming active, for example adding support for a new chip version. Also wcn36xx has been converted to use the recently merged QCOM_SMD subsystem. Otherwise new features and fixes it lots of drivers. Major changes: iwlwifi * some more work in preparation for A000 family support * add support for radiotap timestamps * some work on our firmware debugging capabilities wcn36xx * convert to a proper QCOM_SMD driver (from the platform_driver interface) ath10k * VHT160 support * dump Copy Engine registers during firmware crash * search board file extension from SMBIOS wil6210 * add disable_ap_sme module parameter rt2x00 * support RT3352 with external PA * support for RT3352 with 20MHz crystal * add support for RT5350 WiSoC brcmfmac * add support for BCM43455 sdio device rtl8xxxu * add support for D-Link DWA-131 rev E1, TP-Link TL-WN822N v4 and others ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/usb/isp1760/Kconfig')