From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
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>,
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>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/7] mm: introduce local state for lazy_mmu sections
Date: Fri, 5 Sep 2025 12:37:14 +0100 [thread overview]
Message-ID: <e6072568-1b98-4a7f-8d30-65417a440bb7@lucifer.local> (raw)
In-Reply-To: <2aed0b3b-1a70-4c89-9177-8de4fabb2237@lucifer.local>
On Fri, Sep 05, 2025 at 12:21:40PM +0100, Lorenzo Stoakes wrote:
> You should really base on mm-new.
>
> You need to account for everything that is potentially going to go
> upstream. mm-stable is generally not actually populated all too well until
> shortly before merge window anyway.
Just to note that mm-unstable is also fine. Despite its name, it's substantially
more stable than mm-new, which can even break the build and appears to have no
checks performed on it at all.
But mm-new is the most uptodate version of all the mm code.
Thanks, Lorenzo
next prev parent reply other threads:[~2025-09-05 11:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 12:57 [PATCH 0/7] Nesting support for lazy MMU mode Kevin Brodsky
2025-09-04 12:57 ` [PATCH 1/7] mm: remove arch_flush_lazy_mmu_mode() Kevin Brodsky
2025-09-05 11:00 ` Mike Rapoport
2025-09-04 12:57 ` [PATCH 2/7] mm: introduce local state for lazy_mmu sections Kevin Brodsky
2025-09-04 15:06 ` Yeoreum Yun
2025-09-04 15:47 ` Kevin Brodsky
2025-09-04 17:28 ` Lorenzo Stoakes
2025-09-04 22:14 ` Kevin Brodsky
2025-09-05 11:21 ` Lorenzo Stoakes
2025-09-05 11:37 ` Lorenzo Stoakes [this message]
2025-09-05 12:22 ` Kevin Brodsky
2025-09-05 11:19 ` Mike Rapoport
2025-09-04 12:57 ` [PATCH 3/7] arm64: mm: fully support nested " Kevin Brodsky
2025-09-04 12:57 ` [PATCH 4/7] x86/xen: support nested lazy_mmu sections (again) Kevin Brodsky
2025-09-05 15:48 ` Alexander Gordeev
2025-09-08 7:32 ` Kevin Brodsky
2025-09-04 12:57 ` [PATCH 5/7] powerpc/mm: support nested lazy_mmu sections Kevin Brodsky
2025-09-05 15:52 ` Alexander Gordeev
2025-09-08 7:32 ` Kevin Brodsky
2025-09-04 12:57 ` [PATCH 6/7] sparc/mm: " Kevin Brodsky
2025-09-04 12:57 ` [PATCH 7/7] mm: update lazy_mmu documentation Kevin Brodsky
2025-09-05 11:13 ` Mike Rapoport
2025-09-05 9:46 ` [PATCH 0/7] Nesting support for lazy MMU mode Alexander Gordeev
2025-09-05 12:11 ` 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=e6072568-1b98-4a7f-8d30-65417a440bb7@lucifer.local \
--to=lorenzo.stoakes@oracle.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=kevin.brodsky@arm.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=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=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