From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
peterz@infradead.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: GIT PULL] arm64 fixes for -rc4
Date: Fri, 13 Nov 2020 12:39:35 +0000 [thread overview]
Message-ID: <20201113123934.GA22014@willie-the-truck> (raw)
Hi Linus,
Please can you pull these arm64 fixes for -rc4? It's all fairly simple
and there's a summary in the tag; Paul has reviewed the trivial RCU change.
The main issue remaining at this stage is the ongoing irqtracing problem
[1]. People are working on it, but no patches yet.
Cheers,
Will
[1] https://lore.kernel.org/r/20201103171153.GA46833@C02TD0UTHF1T.local
--->8
The following changes since commit 108aa503657ee2fe8aa071dc620d96372c252ecd:
arm64: kexec_file: try more regions if loading segments fails (2020-11-05 21:48:05 +0000)
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 23c216416056148136bdaf0cdd18caf4904bb6e1:
arm64: cpu_errata: Apply Erratum 845719 to KRYO2XX Silver (2020-11-13 09:47:08 +0000)
----------------------------------------------------------------
arm64 fixes for -rc4
- Spectre/Meltdown safelisting for some Qualcomm KRYO cores
- Fix RCU splat when failing to online a CPU due to a feature mismatch
- Fix a recently introduced sparse warning in kexec()
- Fix handling of CPU erratum 1418040 for late CPUs
- Ensure hot-added memory falls within linear-mapped region
----------------------------------------------------------------
Anshuman Khandual (1):
arm64/mm: Validate hotplug range before creating linear mapping
Konrad Dybcio (4):
arm64: Add MIDR value for KRYO2XX gold/silver CPU cores
arm64: kpti: Add KRYO2XX gold/silver CPU cores to kpti safelist
arm64: proton-pack: Add KRYO2XX silver CPUs to spectre-v2 safe-list
arm64: cpu_errata: Apply Erratum 845719 to KRYO2XX Silver
Will Deacon (4):
arm64: errata: Fix handling of 1418040 with late CPU onlining
arm64: kexec_file: Fix sparse warning
arm64: psci: Avoid printing in cpu_psci_cpu_die()
arm64: smp: Tell RCU about CPUs that fail to come online
arch/arm64/include/asm/cpufeature.h | 2 ++
arch/arm64/include/asm/cputype.h | 4 ++++
arch/arm64/kernel/cpu_errata.c | 2 ++
arch/arm64/kernel/cpufeature.c | 2 ++
arch/arm64/kernel/kexec_image.c | 2 +-
arch/arm64/kernel/process.c | 5 ++---
arch/arm64/kernel/proton-pack.c | 1 +
arch/arm64/kernel/psci.c | 5 +----
arch/arm64/kernel/smp.c | 1 +
arch/arm64/mm/mmu.c | 17 +++++++++++++++++
kernel/rcu/tree.c | 2 +-
11 files changed, 34 insertions(+), 9 deletions(-)
next reply other threads:[~2020-11-13 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 12:39 Will Deacon [this message]
2020-11-13 12:44 ` [GIT PULL] arm64 fixes for -rc4 Will Deacon
2020-11-13 17:25 ` Linus Torvalds
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=20201113123934.GA22014@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--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).