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 0/2] Kbuild: kallsyms: update suffix ignore logic
Date: Mon, 30 Mar 2015 15:20:30 +0200	[thread overview]
Message-ID: <1427721632-11665-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

Two patches that update the kallsyms ignore logic.

Patch #1 adds logic to introduce symbols whose names end in (or equal)
"_veneer". This prevent kallsyms generation errors on large ARM kernels
where the emitted veneers will be different between the first and second
pass, due to the fact that the size of the kallsyms region itself pushes
the .text and .init.text sections further apart during the second pass.

Patch #2 removes the handling of the "gcc[0-9]_compiled." symbol. It was
only ever emitted by GCC v2.x which we don't support anymore anyway.

This series is a followup to ' [RFC PATCH 0/2] ARM large kernels'
(http://thread.gmane.org/gmane.linux.kbuild.devel/13065), but the
other issue addressed by patch #2 of that series will be deferred
for now.

Ard Biesheuvel (2):
  Kbuild: kallsyms: ignore veneers emitted by the ARM linker
  Kbuild: kallsyms: drop special handling of pre-3.0 GCC symbols

 scripts/kallsyms.c | 29 ++++++++++++++++++++---------
 1 file changed, 20 insertions(+), 9 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2015-03-30 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 13:20 Ard Biesheuvel [this message]
2015-03-30 13:20 ` [PATCH 1/2] Kbuild: kallsyms: ignore veneers emitted by the ARM linker Ard Biesheuvel
2015-03-30 13:20 ` [PATCH 2/2] Kbuild: kallsyms: drop special handling of pre-3.0 GCC symbols Ard Biesheuvel
2015-04-07  9:02 ` [PATCH 0/2] Kbuild: kallsyms: update suffix ignore logic Ard Biesheuvel
2015-04-07 11:19   ` Michal Marek

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=1427721632-11665-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).