From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
lorenzo.pieralisi@arm.com
Subject: [GIT PULL] arm64: Second round of fixes for -rc2
Date: Fri, 24 May 2019 18:43:57 +0100 [thread overview]
Message-ID: <20190524174357.GC9120@fuggles.cambridge.arm.com> (raw)
Hi Linus,
As promised, here's the second round of arm64 fixes for -rc2, based on
-rc1. Details in the tag. The ACPI/IORT build fix is pretty big in the
diffstat, but it's really just the result of code movement to ensure
that the functions are guarded correctly when !CONFIG_IOMMU_SUPPORT.
Please pull.
Cheers,
Will
--->8
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to edbcf50eb8aea5f81ae6d83bb969cb0bc02805a1:
arm64: insn: Add BUILD_BUG_ON() for invalid masks (2019-05-24 14:58:30 +0100)
----------------------------------------------------------------
Second round of arm64 fixes for -rc2
- Fix incorrect LDADD instruction encoding in our disassembly macros
- Disable the broken ARM64_PSEUDO_NMI support for now
- Add workaround for Cortex-A76 CPU erratum #1463225
- Handle Cortex-A76/Neoverse-N1 erratum #1418040 w/ existing workaround
- Fix IORT build failure if IOMMU_SUPPORT=n
- Fix place-relative module relocation range checking and its
interaction with KASLR
----------------------------------------------------------------
Ard Biesheuvel (2):
arm64/kernel: kaslr: reduce module randomization range to 2 GB
arm64/module: deal with ambiguity in PRELxx relocation ranges
Jean-Philippe Brucker (2):
arm64: insn: Fix ldadd instruction encoding
arm64: insn: Add BUILD_BUG_ON() for invalid masks
Lorenzo Pieralisi (1):
ACPI/IORT: Fix build error when IOMMU_SUPPORT is disabled
Marc Zyngier (1):
arm64: Handle erratum 1418040 as a superset of erratum 1188873
Will Deacon (3):
arm64: Remove useless message during oops
arm64: errata: Add workaround for Cortex-A76 erratum #1463225
arm64: Kconfig: Make ARM64_PSEUDO_NMI depend on BROKEN for now
Documentation/arm64/silicon-errata.txt | 9 +-
arch/arm64/Kconfig | 26 +++-
arch/arm64/include/asm/cpucaps.h | 5 +-
arch/arm64/include/asm/insn.h | 18 ++-
arch/arm64/kernel/cpu_errata.c | 48 +++++--
arch/arm64/kernel/entry.S | 4 +-
arch/arm64/kernel/kaslr.c | 6 +-
arch/arm64/kernel/module.c | 18 ++-
arch/arm64/kernel/syscall.c | 31 +++++
arch/arm64/kernel/traps.c | 4 -
arch/arm64/mm/fault.c | 33 +++++
drivers/acpi/arm64/iort.c | 238 +++++++++++++++++----------------
12 files changed, 284 insertions(+), 156 deletions(-)
next reply other threads:[~2019-05-24 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 17:43 Will Deacon [this message]
2019-05-24 18:14 ` [GIT PULL] arm64: Second round of fixes for -rc2 Linus Torvalds
2019-05-24 18:19 ` Will Deacon
2019-08-20 9:37 ` Will Deacon
2019-08-20 18:18 ` Linus Torvalds
2019-05-24 18:20 ` pr-tracker-bot
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=20190524174357.GC9120@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=torvalds@linux-foundation.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).