From: Kevin Brodsky <kevin.brodsky@arm.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org,
Kevin Brodsky <kevin.brodsky@arm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Andreas Larsson <andreas@gaisler.com>,
Andrew Morton <akpm@linux-foundation.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Borislav Petkov <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jann Horn <jannh@google.com>, Juergen Gross <jgross@suse.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Suren Baghdasaryan <surenb@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>, Will Deacon <will@kernel.org>,
Yeoreum Yun <yeoreum.yun@arm.com>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
xen-devel@lists.xenproject.org, x86@kernel.org
Subject: [PATCH v3 12/13] mm: bail out of lazy_mmu_mode_* in interrupt context
Date: Wed, 15 Oct 2025 09:27:26 +0100 [thread overview]
Message-ID: <20251015082727.2395128-13-kevin.brodsky@arm.com> (raw)
In-Reply-To: <20251015082727.2395128-1-kevin.brodsky@arm.com>
The lazy MMU mode cannot be used in interrupt context. This is
documented in <linux/pgtable.h>, but isn't consistently handled
across architectures.
arm64 ensures that calls to lazy_mmu_mode_* have no effect in
interrupt context, because such calls do occur in certain
configurations - see commit b81c688426a9 ("arm64/mm: Disable barrier
batching in interrupt contexts"). Other architectures do not check
this situation, most likely because it hasn't occurred so far.
Both arm64 and x86/Xen also ensure that any lazy MMU optimisation is
disabled while in interrupt mode (see queue_pte_barriers() and
xen_get_lazy_mode() respectively).
Let's handle this in the new generic lazy_mmu layer, in the same
fashion as arm64: bail out of lazy_mmu_mode_* if in_interrupt(), and
have in_lazy_mmu_mode() return false to disable any optimisation.
Also remove the arm64 handling that is now redundant; x86/Xen has
its own internal tracking so it is left unchanged.
Signed-off-by: Kevin Brodsky <kevin.brodsky@arm.com>
---
arch/arm64/include/asm/pgtable.h | 17 +----------------
include/linux/pgtable.h | 16 ++++++++++++++--
include/linux/sched.h | 3 +++
3 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
index 944e512767db..a37f417c30be 100644
--- a/arch/arm64/include/asm/pgtable.h
+++ b/arch/arm64/include/asm/pgtable.h
@@ -62,37 +62,22 @@ static inline void emit_pte_barriers(void)
static inline void queue_pte_barriers(void)
{
- if (in_interrupt()) {
- emit_pte_barriers();
- return;
- }
-
if (in_lazy_mmu_mode())
test_and_set_thread_flag(TIF_LAZY_MMU_PENDING);
else
emit_pte_barriers();
}
-static inline void arch_enter_lazy_mmu_mode(void)
-{
- if (in_interrupt())
- return;
-}
+static inline void arch_enter_lazy_mmu_mode(void) {}
static inline void arch_flush_lazy_mmu_mode(void)
{
- if (in_interrupt())
- return;
-
if (test_and_clear_thread_flag(TIF_LAZY_MMU_PENDING))
emit_pte_barriers();
}
static inline void arch_leave_lazy_mmu_mode(void)
{
- if (in_interrupt())
- return;
-
arch_flush_lazy_mmu_mode();
}
diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
index 269225a733de..718c9c788114 100644
--- a/include/linux/pgtable.h
+++ b/include/linux/pgtable.h
@@ -228,8 +228,8 @@ static inline int pmd_dirty(pmd_t pmd)
* of the lazy mode. So the implementation must assume preemption may be enabled
* and cpu migration is possible; it must take steps to be robust against this.
* (In practice, for user PTE updates, the appropriate page table lock(s) are
- * held, but for kernel PTE updates, no lock is held). The mode cannot be used
- * in interrupt context.
+ * held, but for kernel PTE updates, no lock is held). The mode is disabled
+ * in interrupt context and calls to the lazy_mmu API have no effect.
*
* The lazy MMU mode is enabled for a given block of code using:
*
@@ -265,6 +265,9 @@ static inline void lazy_mmu_mode_enable(void)
{
struct lazy_mmu_state *state = ¤t->lazy_mmu_state;
+ if (in_interrupt())
+ return;
+
VM_BUG_ON(state->count == U8_MAX);
/* enable() must not be called while paused */
VM_WARN_ON(state->count > 0 && !state->enabled);
@@ -280,6 +283,9 @@ static inline void lazy_mmu_mode_disable(void)
{
struct lazy_mmu_state *state = ¤t->lazy_mmu_state;
+ if (in_interrupt())
+ return;
+
VM_BUG_ON(state->count == 0);
VM_WARN_ON(!state->enabled);
@@ -297,6 +303,9 @@ static inline void lazy_mmu_mode_pause(void)
{
struct lazy_mmu_state *state = ¤t->lazy_mmu_state;
+ if (in_interrupt())
+ return;
+
VM_WARN_ON(state->count == 0 || !state->enabled);
state->enabled = false;
@@ -307,6 +316,9 @@ static inline void lazy_mmu_mode_resume(void)
{
struct lazy_mmu_state *state = ¤t->lazy_mmu_state;
+ if (in_interrupt())
+ return;
+
VM_WARN_ON(state->count == 0 || state->enabled);
arch_enter_lazy_mmu_mode();
diff --git a/include/linux/sched.h b/include/linux/sched.h
index 2862d8bf2160..beb3e6cfddd9 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -1731,6 +1731,9 @@ static inline char task_state_to_char(struct task_struct *tsk)
#ifdef CONFIG_ARCH_LAZY_MMU
static inline bool in_lazy_mmu_mode(void)
{
+ if (in_interrupt())
+ return false;
+
return current->lazy_mmu_state.enabled;
}
#else
--
2.47.0
next prev parent reply other threads:[~2025-10-15 8:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 8:27 [PATCH v3 00/13] Nesting support for lazy MMU mode Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 01/13] powerpc/64s: Do not re-activate batched TLB flush Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 02/13] x86/xen: simplify flush_lazy_mmu() Kevin Brodsky
2025-10-15 16:52 ` Dave Hansen
2025-10-16 7:32 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 03/13] powerpc/mm: implement arch_flush_lazy_mmu_mode() Kevin Brodsky
2025-10-23 19:36 ` David Hildenbrand
2025-10-24 12:09 ` Kevin Brodsky
2025-10-24 14:42 ` David Hildenbrand
2025-10-24 14:54 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 04/13] sparc/mm: " Kevin Brodsky
2025-10-23 19:37 ` David Hildenbrand
2025-10-15 8:27 ` [PATCH v3 05/13] mm: introduce CONFIG_ARCH_LAZY_MMU Kevin Brodsky
2025-10-18 9:52 ` Mike Rapoport
2025-10-20 10:37 ` Kevin Brodsky
2025-10-23 19:38 ` David Hildenbrand
2025-10-15 8:27 ` [PATCH v3 06/13] mm: introduce generic lazy_mmu helpers Kevin Brodsky
2025-10-17 15:54 ` Alexander Gordeev
2025-10-20 10:32 ` Kevin Brodsky
2025-10-23 19:52 ` David Hildenbrand
2025-10-24 12:13 ` Kevin Brodsky
2025-10-24 13:27 ` David Hildenbrand
2025-10-24 14:32 ` Kevin Brodsky
2025-10-27 16:24 ` David Hildenbrand
2025-10-28 10:34 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 07/13] mm: enable lazy_mmu sections to nest Kevin Brodsky
2025-10-23 20:00 ` David Hildenbrand
2025-10-24 12:16 ` Kevin Brodsky
2025-10-24 13:23 ` David Hildenbrand
2025-10-24 14:33 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 08/13] arm64: mm: replace TIF_LAZY_MMU with in_lazy_mmu_mode() Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 09/13] powerpc/mm: replace batch->active " Kevin Brodsky
2025-10-23 20:02 ` David Hildenbrand
2025-10-24 12:16 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 10/13] sparc/mm: " Kevin Brodsky
2025-10-23 20:03 ` David Hildenbrand
2025-10-15 8:27 ` [PATCH v3 11/13] x86/xen: use lazy_mmu_state when context-switching Kevin Brodsky
2025-10-23 20:06 ` David Hildenbrand
2025-10-24 14:47 ` David Woodhouse
2025-10-24 14:51 ` David Hildenbrand
2025-10-24 15:13 ` David Woodhouse
2025-10-24 15:16 ` David Hildenbrand
2025-10-24 15:38 ` John Paul Adrian Glaubitz
2025-10-24 15:47 ` David Hildenbrand
2025-10-24 15:51 ` John Paul Adrian Glaubitz
2025-10-27 12:38 ` David Hildenbrand
2025-10-24 22:52 ` Demi Marie Obenour
2025-10-27 12:29 ` David Hildenbrand
2025-10-27 13:32 ` Kevin Brodsky
2025-10-24 15:05 ` Kevin Brodsky
2025-10-24 15:17 ` David Woodhouse
2025-10-27 13:38 ` Kevin Brodsky
2025-10-15 8:27 ` Kevin Brodsky [this message]
2025-10-23 20:08 ` [PATCH v3 12/13] mm: bail out of lazy_mmu_mode_* in interrupt context David Hildenbrand
2025-10-24 12:17 ` Kevin Brodsky
2025-10-15 8:27 ` [PATCH v3 13/13] mm: introduce arch_wants_lazy_mmu_mode() Kevin Brodsky
2025-10-23 20:10 ` David Hildenbrand
2025-10-24 12:17 ` Kevin Brodsky
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=20251015082727.2395128-13-kevin.brodsky@arm.com \
--to=kevin.brodsky@arm.com \
--cc=Liam.Howlett@oracle.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jgross@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=sparclinux@vger.kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yeoreum.yun@arm.com \
/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