linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: torvalds@linux-foundation.org (Linus Torvalds)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/6] arch: enable relative relocations for arm64, power and x86
Date: Sun, 11 Mar 2018 13:20:24 -0700	[thread overview]
Message-ID: <CA+55aFxcB+5oB_hL83EASOJQrVRCrzT9iS+2+XtEUToG6VHiqA@mail.gmail.com> (raw)
In-Reply-To: <20180311123815.17916-2-ard.biesheuvel@linaro.org>

On Sun, Mar 11, 2018 at 5:38 AM, Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> Before updating certain subsystems to use place relative 32-bit
> relocations in special sections, to save space and reduce the
> number of absolute relocations that need to be processed at runtime
> by relocatable kernels, introduce the Kconfig symbol and define it
> for some architectures that should be able to support and benefit
> from it.

Are there actually architectures hat _don't_ support those relative
32-bit relocations? That really feels pretty fundamental.

I would have expected all of them to do it - is your selection of
arm64/powerpc/x86 perhaps more about "I have tested these" than about
anything else?

Because I'd almost prefer to just do the switch-over unconditionally
if that is at all possible?

             Linus

  reply	other threads:[~2018-03-11 20:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 12:38 [PATCH v8 0/6] add support for relative references in special sections Ard Biesheuvel
2018-03-11 12:38 ` [PATCH v8 1/6] arch: enable relative relocations for arm64, power and x86 Ard Biesheuvel
2018-03-11 20:20   ` Linus Torvalds [this message]
2018-03-11 20:35     ` Ard Biesheuvel
2018-03-11 21:23       ` Linus Torvalds
2018-03-11 12:38 ` [PATCH v8 2/6] module: allow symbol exports to be disabled Ard Biesheuvel
2018-03-11 21:31   ` Nicolas Pitre
2018-03-11 12:38 ` [PATCH v8 3/6] module: use relative references for __ksymtab entries Ard Biesheuvel
2018-03-11 14:12   ` Ard Biesheuvel
2018-06-25  8:56   ` Martijn Coenen
2018-06-25  9:14     ` Ard Biesheuvel
2018-06-25 10:15       ` Martijn Coenen
2018-06-25 10:52         ` Ard Biesheuvel
2018-03-11 12:38 ` [PATCH v8 4/6] init: allow initcall tables to be emitted using relative references Ard Biesheuvel
2018-03-11 12:38 ` [PATCH v8 5/6] PCI: Add support for relative addressing in quirk tables Ard Biesheuvel
2018-03-11 12:38 ` [PATCH v8 6/6] kernel: tracepoints: add support for relative references Ard Biesheuvel
2018-03-11 12:44 ` [PATCH v8 0/6] add support for relative references in special sections Ard Biesheuvel
2018-03-11 19:08   ` Kees Cook
2018-03-15 16:29 ` Ard Biesheuvel

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=CA+55aFxcB+5oB_hL83EASOJQrVRCrzT9iS+2+XtEUToG6VHiqA@mail.gmail.com \
    --to=torvalds@linux-foundation.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).