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 scsi/fc/Kbuild?id=bf29bddf0417a4783da3b24e8c9e017ac649326f'>diff
path: root/include/uapi/scsi/fc/Kbuild
diff options
context:
space:
mode:
authorJiri Kosina <jkosina@suse.cz>2017-01-27 22:25:52 +0000
committerIngo Molnar <mingo@kernel.org>2017-01-28 09:18:56 +0100
commitbf29bddf0417a4783da3b24e8c9e017ac649326f (patch)
tree54a05a4883b73f80e4e1d8c4b15750aa01c39932 /include/uapi/scsi/fc/Kbuild
parent883af14e67e8b8702b5560aa64c888c0cd0bd66c (diff)
x86/efi: Always map the first physical page into the EFI pagetables
Commit: 129766708 ("x86/efi: Only map RAM into EFI page tables if in mixed-mode") stopped creating 1:1 mappings for all RAM, when running in native 64-bit mode. It turns out though that there are 64-bit EFI implementations in the wild (this particular problem has been reported on a Lenovo Yoga 710-11IKB), which still make use of the first physical page for their own private use, even though they explicitly mark it EFI_CONVENTIONAL_MEMORY in the memory map. In case there is no mapping for this particular frame in the EFI pagetables, as soon as firmware tries to make use of it, a triple fault occurs and the system reboots (in case of the Yoga 710-11IKB this is very early during bootup). Fix that by always mapping the first page of physical memory into the EFI pagetables. We're free to hand this page to the BIOS, as trim_bios_range() will reserve the first page and isolate it away from memory allocators anyway. Note that just reverting 129766708 alone is not enough on v4.9-rc1+ to fix the regression on affected hardware, as this commit: ab72a27da ("x86/efi: Consolidate region mapping logic") later made the first physical frame not to be mapped anyway. Reported-by: Hanka Pavlikova <hanka@ucw.cz> Signed-off-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Borislav Petkov <bp@suse.de> Cc: Laura Abbott <labbott@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Vojtech Pavlik <vojtech@ucw.cz> Cc: Waiman Long <waiman.long@hpe.com> Cc: linux-efi@vger.kernel.org Cc: stable@kernel.org # v4.8+ Fixes: 129766708 ("x86/efi: Only map RAM into EFI page tables if in mixed-mode") Link: http://lkml.kernel.org/r/20170127222552.22336-1-matt@codeblueprint.co.uk [ Tidied up the changelog and the comment. ] Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'include/uapi/scsi/fc/Kbuild')