linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] efi/arm64: add vmlinux link to PE/COFF debug table
Date: Wed, 25 Jan 2017 10:39:17 +0000	[thread overview]
Message-ID: <1485340759-28975-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

Much like GNU debug links, PE/COFF binaries can carry the path on the build
host to the binary containing the debugging symbols. Since the kernel binary
is loaded by UEFI at an a priori unknown offset in the 1:1 mapping of physical
memory, having this information is useful for the debugger automation to find
the file and the offset, and load the symbols automatically.

So if we have debugging symbols to begin with (CONFIG_DEBUG_INFO=y), add the
absolute path to vmlinux to the PE/COFF debug table.

v2: rebase onto v4.10-rc
    use strip rather than objcopy for first pass (#1)
    move debug table inside #ifdef CONFIG_EFI region in head.S (#2)

Ard Biesheuvel (2):
  efi: libstub: Preserve .debug sections after absolute relocation check
  arm64: efi: add vmlinux debug link to the Image binary

 arch/arm64/kernel/Makefile            |  4 +++
 arch/arm64/kernel/head.S              | 34 +++++++++++++++++++-
 arch/arm64/kernel/image.h             |  3 ++
 drivers/firmware/efi/libstub/Makefile | 24 +++++++++-----
 4 files changed, 56 insertions(+), 9 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-01-25 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 10:39 Ard Biesheuvel [this message]
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
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=1485340759-28975-1-git-send-email-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --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).