public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc7
Date: Fri, 14 Mar 2025 16:04:59 +0000	[thread overview]
Message-ID: <20250314160458.GA9438@willie-the-truck> (raw)

Hi Linus,

Please pull this pair of arm64 mm fixes for -rc7.

Summary in the tag, but the main one is a horrible macro fix for our
TLB flushing code which resulted in over-invalidation on the MMU
notifier path.

Cheers,

Will

--->8

The following changes since commit eed6bfa8b28230382b797a88569f2c7569a1a419:

  arm64: hugetlb: Fix flush_hugetlb_tlb_range() invalidation level (2025-02-27 17:40:58 +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 f7edb07ad7c66eab3dce57384f33b9799d579133:

  Fix mmu notifiers for range-based invalidates (2025-03-11 11:37:43 +0000)

----------------------------------------------------------------
arm64 fixes for -rc7

- Fix population of the vmemmap for regions of memory that are smaller
  than a section (128 MiB)

- Fix range-based TLB over-invalidation when invoked via a MMU notifier

----------------------------------------------------------------
Piotr Jaroszynski (1):
      Fix mmu notifiers for range-based invalidates

Zhenhua Huang (1):
      arm64: mm: Populate vmemmap at the page level if not section aligned

 arch/arm64/include/asm/tlbflush.h | 22 ++++++++++++----------
 arch/arm64/mm/mmu.c               |  5 ++++-
 2 files changed, 16 insertions(+), 11 deletions(-)


             reply	other threads:[~2025-03-14 16:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 16:04 Will Deacon [this message]
2025-03-14 20:34 ` [GIT PULL] arm64 fixes for -rc7 Linus Torvalds
2025-03-17 16:00   ` Will Deacon
2025-03-18 11:43     ` Will Deacon
2025-03-18 11:46     ` Marc Zyngier
2025-03-14 21:03 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-11-08 11:57 Will Deacon
2024-11-08 17:39 ` pr-tracker-bot
2022-09-23 18:28 Will Deacon
2022-09-23 22:43 ` Linus Torvalds
2022-09-28 10:46   ` Mark Rutland
2022-09-23 22:53 ` pr-tracker-bot
2022-05-13 16:52 Will Deacon
2022-05-13 17:30 ` pr-tracker-bot
2021-08-20  8:53 Will Deacon
2021-08-20 20:09 ` pr-tracker-bot
2020-12-02 17:17 Will Deacon
2020-12-02 20:48 ` pr-tracker-bot
2020-03-20 15:35 Will Deacon
2020-03-20 17:15 ` pr-tracker-bot
2019-08-28 17:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-08-28 17:45 ` pr-tracker-bot
2018-07-27 11:51 [GIT PULL] arm64: fixes " Will Deacon
2018-05-25 16:04 Will Deacon
2016-07-08 14:49 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=20250314160458.GA9438@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=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