From: npiggin@gmail.com (Nicholas Piggin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: add an option for erratum 657417
Date: Fri, 12 Aug 2016 23:15:03 +1000 [thread overview]
Message-ID: <20160812231503.3e2e059b@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20160812123314.GX1041@n2100.armlinux.org.uk>
On Fri, 12 Aug 2016 13:33:14 +0100
Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> On Fri, Aug 12, 2016 at 06:19:17PM +1000, Nicholas Piggin wrote:
> > This patch adds an option which defaults to "y" in cases where we
> > could possibly be running Cortex A8 and using Thumb2 instructions.
> > In reality the workaround might not be required at all for the kernel
> > if virtual instruction memory is linear in physical memory.
>
> Hmm.
>
> The main kernel image is guaranteed to be contiguous in physical memory
> for all sorts of reasons, so this really isn't a concern for the kernel
> itself.
That's what it *seems* like. I wanted to be conservative because I don't
know the architecture nor have actually looked at the errata docs. You
can probably make stronger guarantees to avoid it. Perhaps enabling just
for modules would be workable.
> Modules, however, are a different matter, as they are mapped in using
> individual pages, and are most likely to be non-contiguous in physical
> memory. The kernel's module linker knows nothing about this errata,
> so it'll generally just fix up the relocations in the most basic of
> ways.
>
> So, I think we should always use this --no-fix-cortex-a8 option where
> the linker supports it irrespective of whether we're running on a core
> needing this workaround, but we probably need to fix the kernel module
> linker to know about this.
It looks like it would be a bit of work to go that route. The linker of
course would not give you relocations or stubs for the branches you
need them.
Anyway do what you think best with the patch. It seems to eliminate the
link time regression on ARM allyesconfig when using thin archives for
building which is the main thing I was concerned about.
Thanks,
Nick
next prev parent reply other threads:[~2016-08-12 13:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 8:19 [PATCH] arm: add an option for erratum 657417 Nicholas Piggin
2016-08-12 12:33 ` Russell King - ARM Linux
2016-08-12 13:15 ` Nicholas Piggin [this message]
2016-08-12 13:49 ` Ard Biesheuvel
2016-08-12 13:50 ` Ard Biesheuvel
2016-08-12 13:52 ` Russell King - ARM Linux
2016-08-12 13:54 ` Ard Biesheuvel
2016-08-12 13:51 ` Russell King - ARM Linux
2016-08-12 14:17 ` Robin Murphy
2016-08-12 14:23 ` Russell King - ARM Linux
2016-08-12 14:32 ` Russell King - ARM Linux
2016-08-23 12:01 ` Arnd Bergmann
2016-08-24 4:00 ` Nicholas Piggin
2016-08-24 7:41 ` Arnd Bergmann
2016-08-24 9:05 ` Nicholas Piggin
2016-08-24 10:56 ` Nicholas Piggin
2016-08-24 12:06 ` Nicholas Piggin
2016-08-24 15:01 ` Arnd Bergmann
2016-08-26 11:17 ` Nicholas Piggin
2016-08-26 14:07 ` Arnd Bergmann
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=20160812231503.3e2e059b@roar.ozlabs.ibm.com \
--to=npiggin@gmail.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).