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: [RFC PATCH 0/2] arm64: runtime workaround for erratum #843419
Date: Thu, 17 Sep 2015 21:38:53 +0200	[thread overview]
Message-ID: <1442518735-16625-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

This implements a workaround for the A53 erratum that results in adrp
instructions to produce incorrect values if they appear in either of
the last two instruction slots of a 4 KB page.

Instead of building modules using the large code model, this approach
uses veneers to call the adrp instructions at unaffected offsets, unless
they can be converted into adr instructions, which is even better (this
depends on whether the symbol is with 1 MB of the place)

Comments welcome.

Ard Biesheuvel (2):
  arm64: introduce infrastructure for emitting veneers at module reloc
    time
  arm64: errata: add module load workaround for erratum #843419

 arch/arm64/Kconfig               |  21 +++
 arch/arm64/Makefile              |   4 +
 arch/arm64/include/asm/module.h  |   9 ++
 arch/arm64/include/asm/veneers.h |  19 +++
 arch/arm64/kernel/Makefile       |   1 +
 arch/arm64/kernel/module.c       |  33 +++++
 arch/arm64/kernel/module.lds     |   4 +
 arch/arm64/kernel/veneers.c      | 134 ++++++++++++++++++++
 8 files changed, 225 insertions(+)
 create mode 100644 arch/arm64/include/asm/veneers.h
 create mode 100644 arch/arm64/kernel/module.lds
 create mode 100644 arch/arm64/kernel/veneers.c

-- 
1.9.1

             reply	other threads:[~2015-09-17 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 19:38 Ard Biesheuvel [this message]
2015-09-17 19:38 ` [RFC PATCH 1/2] arm64: introduce infrastructure for emitting veneers at module reloc time Ard Biesheuvel
2015-09-17 19:38 ` [RFC PATCH 2/2] arm64: errata: add module load workaround for erratum #843419 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=1442518735-16625-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).