|author||Ard Biesheuvel <email@example.com>||2017-02-02 17:33:19 +0000|
|committer||Will Deacon <firstname.lastname@example.org>||2017-02-03 15:22:37 +0000|
|parent||arm64: ensure __raw_read_system_reg() is self-consistent (diff)|
efi: arm64: Add vmlinux debug link to the Image binary
When building with debugging symbols, take the absolute path to the vmlinux binary and add it to the special PE/COFF debug table entry. This allows a debug EFI build to find the vmlinux binary, which is very helpful in debugging, given that the offset where the Image is first loaded by EFI is highly unpredictable. On implementations of UEFI that choose to implement it, this information is exposed via the EFI debug support table, which is a UEFI configuration table that is accessible both by the firmware at boot time and by the OS at runtime, and lists all PE/COFF images loaded by the system. The format of the NB10 Codeview entry is based on the definition used by EDK2, which is our primary reference when it comes to the use of PE/COFF in the context of UEFI firmware. Signed-off-by: Ard Biesheuvel <email@example.com> [will: use realpath instead of shell invocation, as discussed on list] Signed-off-by: Will Deacon <firstname.lastname@example.org>
Diffstat (limited to 'arch/arm64/Kconfig.debug')
1 files changed, 8 insertions, 0 deletions
diff --git a/arch/arm64/Kconfig.debug b/arch/arm64/Kconfig.debug
index d1ebd46872fd..f7f38b1aab14 100644
@@ -95,6 +95,14 @@ config DEBUG_ALIGN_RODATA
If in doubt, say N.
+ depends on EFI && DEBUG_INFO
+ bool "UEFI debugging"
+ Enable this option to include EFI specific debugging features into
+ the kernel that are only useful when using a debug build of the
+ UEFI firmware