From: "Jürgen Groß" <jgross@suse.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.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: linux-mm@kvack.org, sparclinux@vger.kernel.org,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Fix lazy mmu mode
Date: Mon, 3 Mar 2025 15:36:40 +0100 [thread overview]
Message-ID: <d0de16ad-33d5-4878-8e7f-8e8cd1d44585@suse.com> (raw)
In-Reply-To: <20250303141542.3371656-1-ryan.roberts@arm.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2006 bytes --]
On 03.03.25 15:15, Ryan Roberts wrote:
> 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 but I think they
> are in good enough shape for some linux-next testing.
>
> Applies on Friday's mm-unstable (5f089a9aa987), as I assume this would be
> preferred via that tree.
>
> Changes since v1
> ================
> - split v1 patch #1 into v2 patch #1 and #2; per David
> - Added Acked-by tags from David and Andreas; Thanks!
> - Refined the patches which are truely fixes and added to stable to cc
>
> Thanks,
> Ryan
>
> Ryan Roberts (5):
> mm: Fix lazy mmu docs and usage
> fs/proc/task_mmu: Reduce scope of lazy mmu region
> 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(-)
For the series:
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-03-03 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 14:15 Ryan Roberts
2025-03-03 14:15 ` [PATCH v2 1/5] mm: Fix lazy mmu docs and usage Ryan Roberts
2025-03-03 14:15 ` [PATCH v2 2/5] fs/proc/task_mmu: Reduce scope of lazy mmu region Ryan Roberts
2025-03-03 14:15 ` [PATCH v2 3/5] sparc/mm: Disable preemption in lazy mmu mode Ryan Roberts
2025-03-03 14:15 ` [PATCH v2 4/5] sparc/mm: Avoid calling arch_enter/leave_lazy_mmu() in set_ptes Ryan Roberts
2025-03-03 14:15 ` [PATCH v2 5/5] Revert "x86/xen: allow nesting of same lazy mode" Ryan Roberts
2025-03-03 14:36 ` Jürgen Groß [this message]
2025-04-10 16:07 ` [PATCH v2 0/5] Fix lazy mmu mode Alexander Gordeev
2025-04-14 13:22 ` Ryan Roberts
2025-04-14 14:04 ` Alexander Gordeev
2025-04-14 14:11 ` Ryan Roberts
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=d0de16ad-33d5-4878-8e7f-8e8cd1d44585@suse.com \
--to=jgross@suse.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=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=ryan.roberts@arm.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