From: Stanislav Kinsburskii <skinsburskii@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: airlied@gmail.com, akhilesh@ee.iitb.ac.in, corbet@lwn.net,
dakr@kernel.org, david@kernel.org, decui@microsoft.com,
haiyangz@microsoft.com, jgg@ziepe.ca, kees@kernel.org,
kys@microsoft.com, leon@kernel.org, liam@infradead.org,
lizhi.hou@amd.com, ljs@kernel.org, longli@microsoft.com,
lyude@redhat.com, maarten.lankhorst@linux.intel.com,
mamin506@gmail.com, mhocko@suse.com, mripard@kernel.org,
nouveau@lists.freedesktop.org, ogabbay@kernel.org,
oleg@redhat.com, rppt@kernel.org, shuah@kernel.org,
simona@ffwll.ch, skhan@linuxfoundation.org, surenb@google.com,
tzimmermann@suse.de, vbabka@kernel.org, wei.liu@kernel.org,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v8 0/8] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings
Date: Tue, 14 Jul 2026 09:09:51 -0700 [thread overview]
Message-ID: <alZfTxfypj39OrCE@skinsburskii> (raw)
In-Reply-To: <20260713154535.7656b3a630e2f6f076b4e76e@linux-foundation.org>
On Mon, Jul 13, 2026 at 03:45:35PM -0700, Andrew Morton wrote:
> On Mon, 13 Jul 2026 13:57:55 -0700 Stanislav Kinsburskii <skinsburskii@gmail.com> wrote:
>
> > > > I rebased this series on top of mm-new right before sending it out.
> > > > Should I have used a different branch?
> > >
> > > mm-new is good - Sashiko attempts that. But it's changing rapidly at
> > > this point in the development cycle.
> > >
> >
> > I’d like to send another revision addressing a few comments and also
> > replace the `max/max_t` check with something simpler.
> >
> > Which branch should I base it on so that Sashiko can apply it
> > successfully?
>
> mainline Linus would be safest.
>
Looks like linux-next/master has been updated with the v8 of the series.
I have v9 with a few small fixes, but it is too late to send it out already?
If it's not, then what should I base it on?
Thanks,
Stanislav
> > Or would it be better to send fixups against `mm-new`?
>
> That should work as well, but it doesn't give us a Sashiko scan of the
> whole patchset.
WARNING: multiple messages have this Message-ID (diff)
From: Stanislav Kinsburskii <skinsburskii@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: akhilesh@ee.iitb.ac.in, corbet@lwn.net, dakr@kernel.org,
david@kernel.org, decui@microsoft.com, haiyangz@microsoft.com,
jgg@ziepe.ca, kees@kernel.org, kys@microsoft.com,
leon@kernel.org, liam@infradead.org, lizhi.hou@amd.com,
ljs@kernel.org, longli@microsoft.com,
maarten.lankhorst@linux.intel.com, mamin506@gmail.com,
mhocko@suse.com, mripard@kernel.org,
nouveau@lists.freedesktop.org, ogabbay@kernel.org,
oleg@redhat.com, rppt@kernel.org, shuah@kernel.org,
simona@ffwll.ch, skhan@linuxfoundation.org, surenb@google.com,
vbabka@kernel.org, wei.liu@kernel.org,
dri-devel@lists.freedesktop.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH v8 0/8] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings
Date: Tue, 14 Jul 2026 09:09:51 -0700 [thread overview]
Message-ID: <alZfTxfypj39OrCE@skinsburskii> (raw)
In-Reply-To: <20260713154535.7656b3a630e2f6f076b4e76e@linux-foundation.org>
On Mon, Jul 13, 2026 at 03:45:35PM -0700, Andrew Morton wrote:
> On Mon, 13 Jul 2026 13:57:55 -0700 Stanislav Kinsburskii <skinsburskii@gmail.com> wrote:
>
> > > > I rebased this series on top of mm-new right before sending it out.
> > > > Should I have used a different branch?
> > >
> > > mm-new is good - Sashiko attempts that. But it's changing rapidly at
> > > this point in the development cycle.
> > >
> >
> > I’d like to send another revision addressing a few comments and also
> > replace the `max/max_t` check with something simpler.
> >
> > Which branch should I base it on so that Sashiko can apply it
> > successfully?
>
> mainline Linus would be safest.
>
Looks like linux-next/master has been updated with the v8 of the series.
I have v9 with a few small fixes, but it is too late to send it out already?
If it's not, then what should I base it on?
Thanks,
Stanislav
> > Or would it be better to send fixups against `mm-new`?
>
> That should work as well, but it doesn't give us a Sashiko scan of the
> whole patchset.
next prev parent reply other threads:[~2026-07-14 16:09 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 21:26 [PATCH v8 0/8] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Stanislav Kinsburskii
2026-07-10 21:26 ` [PATCH v8 1/8] mm/hmm: move page fault handling out of walk callbacks Stanislav Kinsburskii
2026-07-10 21:26 ` [PATCH v8 2/8] mm/hmm: add hmm_range_fault_unlocked_timeout() for mmap lock-drop support Stanislav Kinsburskii
2026-07-10 22:12 ` Andrew Morton
2026-07-10 22:12 ` Andrew Morton
2026-07-11 3:09 ` Stanislav Kinsburskii
2026-07-11 3:09 ` Stanislav Kinsburskii
2026-07-10 21:26 ` [PATCH v8 3/8] selftests/mm: add HMM test for mmap lock-dropping faults Stanislav Kinsburskii
2026-07-10 21:26 ` [PATCH v8 4/8] mshv: Use hmm_range_fault_unlocked_timeout() for region faults Stanislav Kinsburskii
2026-07-10 22:12 ` Andrew Morton
2026-07-10 22:12 ` Andrew Morton
2026-07-11 3:14 ` Stanislav Kinsburskii
2026-07-11 3:14 ` Stanislav Kinsburskii
2026-07-11 5:46 ` Andrew Morton
2026-07-11 5:46 ` Andrew Morton
2026-07-13 16:56 ` Stanislav Kinsburskii
2026-07-13 16:56 ` Stanislav Kinsburskii
2026-07-13 14:55 ` Jason Gunthorpe
2026-07-13 14:55 ` Jason Gunthorpe
2026-07-10 21:26 ` [PATCH v8 5/8] drm/nouveau: Use hmm_range_fault_unlocked_timeout() for SVM faults Stanislav Kinsburskii
2026-07-10 22:12 ` Andrew Morton
2026-07-10 22:12 ` Andrew Morton
2026-07-11 3:16 ` Stanislav Kinsburskii
2026-07-11 3:16 ` Stanislav Kinsburskii
2026-07-11 5:48 ` Andrew Morton
2026-07-11 5:48 ` Andrew Morton
2026-07-13 16:59 ` Stanislav Kinsburskii
2026-07-13 16:59 ` Stanislav Kinsburskii
2026-07-13 23:18 ` Andrew Morton
2026-07-13 23:18 ` Andrew Morton
2026-07-10 21:27 ` [PATCH v8 6/8] RDMA/umem: Use hmm_range_fault_unlocked_timeout() for ODP faults Stanislav Kinsburskii
2026-07-10 21:27 ` [PATCH v8 7/8] accel/amdxdna: Use hmm_range_fault_unlocked_timeout() for range population Stanislav Kinsburskii
2026-07-10 22:12 ` Andrew Morton
2026-07-10 22:12 ` Andrew Morton
2026-07-11 3:19 ` Stanislav Kinsburskii
2026-07-11 3:19 ` Stanislav Kinsburskii
2026-07-10 21:27 ` [PATCH v8 8/8] drm/gpusvm: Use hmm_range_fault_unlocked_timeout() for range faults Stanislav Kinsburskii
2026-07-10 22:12 ` Andrew Morton
2026-07-10 22:12 ` Andrew Morton
2026-07-13 16:30 ` Matthew Brost
2026-07-13 16:30 ` Matthew Brost
2026-07-13 17:01 ` Stanislav Kinsburskii
2026-07-13 17:01 ` Stanislav Kinsburskii
2026-07-10 22:11 ` [PATCH v8 0/8] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Andrew Morton
2026-07-10 22:11 ` Andrew Morton
2026-07-11 3:22 ` Stanislav Kinsburskii
2026-07-11 3:22 ` Stanislav Kinsburskii
2026-07-11 5:49 ` Andrew Morton
2026-07-11 5:49 ` Andrew Morton
2026-07-13 20:57 ` Stanislav Kinsburskii
2026-07-13 20:57 ` Stanislav Kinsburskii
2026-07-13 22:45 ` Andrew Morton
2026-07-13 22:45 ` Andrew Morton
2026-07-14 16:09 ` Stanislav Kinsburskii [this message]
2026-07-14 16:09 ` Stanislav Kinsburskii
2026-07-14 17:57 ` Andrew Morton
2026-07-14 17:57 ` Andrew Morton
2026-07-14 20:05 ` Stanislav Kinsburskii
2026-07-14 20:05 ` Stanislav Kinsburskii
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=alZfTxfypj39OrCE@skinsburskii \
--to=skinsburskii@gmail.com \
--cc=airlied@gmail.com \
--cc=akhilesh@ee.iitb.ac.in \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=david@kernel.org \
--cc=decui@microsoft.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kees@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=ljs@kernel.org \
--cc=longli@microsoft.com \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mamin506@gmail.com \
--cc=mhocko@suse.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ogabbay@kernel.org \
--cc=oleg@redhat.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=tzimmermann@suse.de \
--cc=vbabka@kernel.org \
--cc=wei.liu@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.