From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: efi: add vmlinux debug link to the Image binary
Date: Wed, 25 Jan 2017 11:53:05 +0000 [thread overview]
Message-ID: <20170125115305.GA29027@leverpostej> (raw)
In-Reply-To: <1485340759-28975-3-git-send-email-ard.biesheuvel@linaro.org>
On Wed, Jan 25, 2017 at 10:39:19AM +0000, Ard Biesheuvel wrote:
> When building with debugging symbols, take the absolute path to the
> vmlinux binary and add it to the special PE/COFF debug table entry.
>
> These entries are used internally by EDK2 based* debug builds of UEFI
> to populate the DebugImageInfo table, which can be used by debuggers
> as well as by the OS itself to retrieve information about all loaded
> PE/COFF executables. This is highly useful for source level debugging
> of the UEFI stub.
Does that mean EFI_IMAGE_DEBUG_DIRECTORY_ENTRY and friends are
EDK2-specific?
Or just that the way EDK2 happens to use those is EDK2-specific?
> * for AArch64, this probably means all of them
>
> Cc: Matt Fleming <matt@codeblueprint.co.uk>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> arch/arm64/kernel/Makefile | 4 +++
> arch/arm64/kernel/head.S | 34 +++++++++++++++++++-
> arch/arm64/kernel/image.h | 3 ++
> 3 files changed, 40 insertions(+), 1 deletion(-)
> +efi_debug_table:
> + // EFI_IMAGE_DEBUG_DIRECTORY_ENTRY
> + .long 0 // Characteristics
> + .long 0 // TimeDateStamp
> + .short 0 // MajorVersion
> + .short 0 // MinorVersion
> + .long 2 // Type == EFI_IMAGE_DEBUG_TYPE_CODEVIEW
> +ENTRY(efi_debug_entry)
> + // EFI_IMAGE_DEBUG_CODEVIEW_NB10_ENTRY
> + .long 0x3031424E // Signature
Certainly not a blocker for this, but this reminds me that it would be
nice to de-magic the EFI constants used by the stub.
I took a stab a while back [1], for the existing definitions, but that
fell by the wayside.
Thanks,
Mark.
[1] git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git efi-stub/definitions
next prev parent reply other threads:[~2017-01-25 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 10:39 [PATCH v2 0/2] efi/arm64: add vmlinux link to PE/COFF debug table Ard Biesheuvel
2017-01-25 10:39 ` [PATCH v2 1/2] efi: libstub: Preserve .debug sections after absolute relocation check Ard Biesheuvel
2017-01-25 10:39 ` [PATCH v2 2/2] arm64: efi: add vmlinux debug link to the Image binary Ard Biesheuvel
2017-01-25 11:45 ` Ard Biesheuvel
2017-01-25 11:53 ` Mark Rutland [this message]
2017-01-25 12:00 ` Ard Biesheuvel
2017-01-26 18:26 ` Mark Rutland
2017-01-26 18:33 ` Ard Biesheuvel
2017-01-26 18:44 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170125115305.GA29027@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).