From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 7.1-rc5
Date: Fri, 22 May 2026 14:08:34 +0100 [thread overview]
Message-ID: <ahBVUtmWJue3HmV8@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 6ccbb613b42a1f1ba7bfd547a148f644a902a25c:
arm_mpam: Check whether the config array is allocated before destroying it (2026-05-14 09:52:05 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to c2ff4764e03e7a8d758352f4aceb8fe1be6ac971:
arm64: tlb: Flush walk cache when unsharing PMD tables (2026-05-22 11:13:51 +0100)
----------------------------------------------------------------
arm64 fixes:
- Handle probe on hinted conditional branch instructions. BC.cond
instructions can be simulated in the same way as B.cond instructions,
so extend the decode mask for B.cond to cover BC.cond
- Flush the walk cache when unsharing PMD tables. Recent changes to
huge_pmd_unshare() introduced mmu_gather::unshared_tables but the
arm64 code was still treating the TLB flushing as only targeting leaf
entries (TLBI VALE1IS). Fix it by using non-leaf-only instructions
(TLBI VAE1IS) when tlb->unshared_tables is set
----------------------------------------------------------------
Vladimir Murzin (1):
arm64: probes: Handle probes on hinted conditional branch instructions
Zeng Heng (1):
arm64: tlb: Flush walk cache when unsharing PMD tables
arch/arm64/include/asm/insn.h | 2 +-
arch/arm64/include/asm/tlb.h | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
Catalin
next reply other threads:[~2026-05-22 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 13:08 Catalin Marinas [this message]
2026-05-22 14:25 ` [GIT PULL] arm64 fixes for 7.1-rc5 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=ahBVUtmWJue3HmV8@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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