Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, mark.rutland@arm.com, maz@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc2
Date: Fri, 4 Sep 2026 19:20:00 +0100	[thread overview]
Message-ID: <apsL0Jd_RUiP20Vd@willie-the-truck> (raw)

Hi Linus,

Please pull this batch of arm64 fixes for -rc2. As you can see from the
tag, there's nothing Earth-shattering, but worthwhile fixes nonetheless.

Cheers,

Will

--->8

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -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 5445d64199626974269fcdf347769ad44b0bb53b:

  arm64: Don't read GMID_EL1 when MTE is disabled (2026-09-03 13:03:23 +0000)

----------------------------------------------------------------
arm64 fixes for -rc2

- Disable interrupts during page-table walk in show_pte()

- Fix kexec_file_load() with 52-bit capable kernels on machines without
  52-bit addressing

- Fix MIDR matching in CPU errata handling for KVM guests

- Avoid reading MTE-specific ID registers when MTE support is disabled

----------------------------------------------------------------
Breno Leitao (1):
      arm64: trans_pgd: clone only the linear map that exists at runtime

Fuad Tabba (1):
      arm64: Don't read GMID_EL1 when MTE is disabled

Karl Mehltretter (1):
      arm64: mm: Fix the lockless page-table walk in show_pte()

Khushit Shah (1):
      arm64: errata: pass REVIDR when matching target implementation CPUs

 arch/arm64/include/asm/cpu.h        |  1 +
 arch/arm64/include/asm/cpufeature.h |  7 -------
 arch/arm64/kernel/cpu_errata.c      |  2 +-
 arch/arm64/kernel/cpufeature.c      | 33 +++++++++++++++++++++++++++++----
 arch/arm64/kernel/cpuinfo.c         |  2 +-
 arch/arm64/kernel/machine_kexec.c   |  3 ++-
 arch/arm64/mm/fault.c               | 12 ++++++++----
 7 files changed, 42 insertions(+), 18 deletions(-)


             reply	other threads:[~2026-09-04 18:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 18:20 Will Deacon [this message]
2026-09-04 21:00 ` [GIT PULL] arm64 fixes for -rc2 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-02-27 21:20 Will Deacon
2026-02-27 21:46 ` pr-tracker-bot
2022-04-08 16:29 Will Deacon
2022-04-08 17:46 ` pr-tracker-bot
2021-07-16 14:53 Will Deacon
2021-07-17  2:12 ` pr-tracker-bot
2020-10-30 17:05 Will Deacon
2020-10-30 20:29 ` pr-tracker-bot
2020-06-19 12:43 Will Deacon
2020-06-19 19:30 ` pr-tracker-bot
2020-02-13 17:10 Will Deacon
2020-02-13 22:40 ` pr-tracker-bot
2019-07-26 13:12 [GIT PULL] arm64: " Will Deacon
2019-07-26 18:25 ` pr-tracker-bot
2019-01-11 18:20 Will Deacon
2019-01-11 20:40 ` pr-tracker-bot
2018-08-31 16:12 Will Deacon
2017-12-01 18:23 Will Deacon
2016-10-20 17:14 Will Deacon
2016-06-03 15:37 Will Deacon
2016-04-01 15:15 Will Deacon
2016-01-27 18:45 Will Deacon
2015-09-17 14:04 Will Deacon

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=apsL0Jd_RUiP20Vd@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=maz@kernel.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