public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	John Stultz <jstultz@google.com>,
	linux-kbuild@vger.kernel.org
Subject: [PATCH v2 0/2] Fix 'faddr2line' for LLVM arm64 builds
Date: Tue, 25 Jul 2023 22:11:55 +0100	[thread overview]
Message-ID: <20230725211157.17031-1-will@kernel.org> (raw)

Hi folks,

This is version two of the patches I sent yesterday attempting to fix
'faddr2line' for LLVM arm64 kernel images.

v1: https://lore.kernel.org/r/20230724174517.15736-1-will@kernel.org

Changes since v1 include:
  * Dropped the patch adding support for LLVM=1, since Josh said he'd
    pick it up.
  * Reuse the ignored symbol regex from 'mksysmap' instead of ignoring
    symbols based on their type.

Feedback welcome. I've checked that the symbols in System.map for a
defconfig arm64 build are the same with and without these changes, but I
think I'd still like this to spend time in -next if we go down this
route.

Cheers,

Will

Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nicolas Schier <nicolas@fjasle.eu>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: John Stultz <jstultz@google.com>
Cc: linux-kbuild@vger.kernel.org

--->8

Will Deacon (2):
  scripts/mksysmap: Factor out sed ignored symbols expression into
    script
  scripts/faddr2line: Constrain readelf output to symbols from
    System.map

 scripts/faddr2line              |  3 +-
 scripts/mksysmap                | 77 +--------------------------------
 scripts/sysmap-ignored-syms.sed | 74 +++++++++++++++++++++++++++++++
 3 files changed, 77 insertions(+), 77 deletions(-)
 create mode 100644 scripts/sysmap-ignored-syms.sed

-- 
2.41.0.487.g6d72f3e995-goog


             reply	other threads:[~2023-07-25 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 21:11 Will Deacon [this message]
2023-07-25 21:11 ` [PATCH v2 1/2] scripts/mksysmap: Factor out sed ignored symbols expression into script Will Deacon
2023-07-25 21:11 ` [PATCH v2 2/2] scripts/faddr2line: Constrain readelf output to symbols from System.map Will Deacon
2023-07-25 21:38   ` Josh Poimboeuf
2023-07-27 12:18     ` Will Deacon
2023-07-27 16:49       ` Josh Poimboeuf

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=20230725211157.17031-1-will@kernel.org \
    --to=will@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    /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