From: Ryan Roberts <ryan.roberts@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
linux-mm@kvack.org, sparclinux@vger.kernel.org,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/4] Fix lazy mmu mode
Date: Sun, 2 Mar 2025 14:55:50 +0000 [thread overview]
Message-ID: <20250302145555.3236789-1-ryan.roberts@arm.com> (raw)
Hi All,
I'm planning to implement lazy mmu mode for arm64 to optimize vmalloc. As part
of that, I will extend lazy mmu mode to cover kernel mappings in vmalloc table
walkers. While lazy mmu mode is already used for kernel mappings in a few
places, this will extend it's use significantly.
Having reviewed the existing lazy mmu implementations in powerpc, sparc and x86,
it looks like there are a bunch of bugs, some of which may be more likely to
trigger once I extend the use of lazy mmu. So this series attempts to clarify
the requirements and fix all the bugs in advance of that series. See patch #1
commit log for all the details.
Note that I have only been able to compile test these changes so appreciate any
help in testing.
Applies on Friday's mm-unstable (5f089a9aa987), as I assume this would be
preferred via that tree.
Thanks,
Ryan
Ryan Roberts (4):
mm: Fix lazy mmu docs and usage
sparc/mm: Disable preemption in lazy mmu mode
sparc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes
Revert "x86/xen: allow nesting of same lazy mode"
arch/sparc/include/asm/pgtable_64.h | 2 --
arch/sparc/mm/tlb.c | 5 ++++-
arch/x86/include/asm/xen/hypervisor.h | 15 ++-------------
arch/x86/xen/enlighten_pv.c | 1 -
fs/proc/task_mmu.c | 11 ++++-------
include/linux/pgtable.h | 14 ++++++++------
6 files changed, 18 insertions(+), 30 deletions(-)
--
2.43.0
next reply other threads:[~2025-03-02 14:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 14:55 Ryan Roberts [this message]
2025-03-02 14:55 ` [PATCH v1 1/4] mm: Fix lazy mmu docs and usage Ryan Roberts
2025-03-03 8:49 ` David Hildenbrand
2025-03-03 8:52 ` David Hildenbrand
2025-03-03 10:22 ` Ryan Roberts
2025-03-03 10:30 ` David Hildenbrand
2025-03-03 12:49 ` Andreas Larsson
2025-03-02 14:55 ` [PATCH v1 2/4] sparc/mm: Disable preemption in lazy mmu mode Ryan Roberts
2025-03-03 8:51 ` David Hildenbrand
2025-03-03 13:39 ` Andreas Larsson
2025-03-02 14:55 ` [PATCH v1 3/4] sparc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes Ryan Roberts
2025-03-03 8:52 ` David Hildenbrand
2025-03-03 13:39 ` Andreas Larsson
2025-03-02 14:55 ` [PATCH v1 4/4] Revert "x86/xen: allow nesting of same lazy mode" Ryan Roberts
2025-03-03 11:52 ` David Hildenbrand
2025-03-03 12:33 ` Ryan Roberts
2025-03-03 12:57 ` David Hildenbrand
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=20250302145555.3236789-1-ryan.roberts@arm.com \
--to=ryan.roberts@arm.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=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=xen-devel@lists.xenproject.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).