Re: [PATCH 0/6] mm: preparatory patches for PMD level swap entries

[SJ Park]

On Thu, 2 Jul 2026 16:08:03 +0300 Mike Rapoport <rppt@xxxxxxxxxx> wrote:

> On Thu, Jul 02, 2026 at 11:48:24AM +0100, Lorenzo Stoakes wrote:
> > +cc Mike re: CI.
> > 
> > On Wed, Jul 01, 2026 at 04:46:13PM -0700, Andrew Morton wrote:
> > > On Wed, 1 Jul 2026 09:04:33 +0100 Lorenzo Stoakes <ljs@xxxxxxxxxx> wrote:
> > >
> > > > On Tue, Jun 30, 2026 at 12:50:24PM -0700, Andrew Morton wrote:
> > > > > On Tue, 30 Jun 2026 09:34:37 -0700 Usama Arif <usama.arif@xxxxxxxxx> wrote:
> > > > >
> > > > > > This is the preparatory part of the PMD page table swapin work.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > This comes reasonably reviewed, so I'll queue it in mm-new.
> > > > >
> > > > > Why?
> > > > >
> > > > > - Human review coverage and AI review make me believe this isn't the
> > > > >   final version at all, but I do believe this is something we want in
> > > > >   7.2, and getting it under test early will help to push it along.
> > > > >
> > > > > - Getting it in there early means that others will base their work on
> > > > >   material which will probably be upstreamed this cycle, so this gives
> > > > >   them a more accurate base against which to work.
> > > > >
> > > > > Sashiko did find a lot to talk about, some of it pre-existing so can
> > > > > people who work on this code please take a look at
> > > > >
> > > > > 	https://sashiko.dev/#/patchset/20260630164143.1595669-1-usama.arif@xxxxxxxxx
> > > > >
> > > > >
> > > >
> > > > Hm, my understanding was that mm-new is where we take everything submitted for
> > > > early testing?
> > > >
> > > > Did something change?
> > >
> > > mm-new has always been a few day front-end to mm-unstable.  To protect
> > > linux-next from brand new material.  It serves no other purpose.
> > 
> > Well it only serves a purpose if it gives us better testing.
> > 
> > We have a CI running tests now though, Mike - is that predicated on material
> > being in mm-new or does it just grab the email?
> 
> CI grabs patches from patchwork and tries to apply them to one of the three
> bases: mm-unstable, mm-new or the latest Linus' commit merged into mm.git.
> 
> If patches apply, the other bases are not checked. 
> 
> This patches applied cleanly to mm-unstable and successfully passed (at
> least once :) )
> https://github.com/linux-mm/linux-mm/actions/runs/28544575927/

Awesome!

I found the CI script (mm-ci) on the GitHub organization.  Is the repo open to
contributions?  If so, between GitHub PR and patches to linux-mm@ what is more
preferred?  Seems it is not running DAMON specific tests, and I want to add
DAMON kunit test to the test set as a first step (DAMO selftest is bit flaky on
some systems), if people don't mind.

I or someone else may also want to add more tests like Cc list checking [1] in
future.

[1] https://lore.kernel.org/20260703190421.100480-1-sj@xxxxxxxxxx


Thanks,
SJ

[...]