From: Stanislav Kinsburskii <skinsburskii@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Liam.Howlett@oracle.com, david@kernel.org, jgg@ziepe.ca,
corbet@lwn.net, leon@kernel.org, ljs@kernel.org, mhocko@suse.com,
rppt@kernel.org, shuah@kernel.org, skhan@linuxfoundation.org,
surenb@google.com, vbabka@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings
Date: Fri, 29 May 2026 07:41:12 -0700 [thread overview]
Message-ID: <ahmliNJiR-R9N4M3@skinsburskii> (raw)
In-Reply-To: <20260528131115.184c178d03d516e11248a1ae@linux-foundation.org>
On Thu, May 28, 2026 at 01:11:15PM -0700, Andrew Morton wrote:
> On Thu, 28 May 2026 12:53:59 -0700 Stanislav Kinsburskii <skinsburskii@gmail.com> wrote:
>
> > A gentle reminder as requested: do you think this change could be taken into
> > the mm tree?
> > It's beneficial not only for the MSHV driver, but can be used for
> > post-copy live migration of GPU states in future.
>
> Still no review, alas. It's not a trivial thing, affecting both hmm
> and userfaultfd. And we're closing in on -rc6.
>
> I'd prefer that we revisit in the next cycle, please. Refresh retest
> and resend after -rc1?
>
Sure, will do.
Thanks,
Stanislav
prev parent reply other threads:[~2026-05-29 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:09 [PATCH v3 0/3] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Stanislav Kinsburskii
2026-05-20 14:09 ` [PATCH v3 1/3] mm/hmm: move page fault handling out of walk callbacks Stanislav Kinsburskii
2026-05-20 14:09 ` [PATCH v3 2/3] mm/hmm: add hmm_range_fault_unlockable() for mmap lock-drop support Stanislav Kinsburskii
2026-05-20 14:09 ` [PATCH v3 3/3] selftests/mm: add userfaultfd test for HMM unlockable path Stanislav Kinsburskii
2026-05-21 23:33 ` [PATCH v3 0/3] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Andrew Morton
2026-05-22 1:03 ` Stanislav Kinsburskii
2026-05-28 19:53 ` Stanislav Kinsburskii
2026-05-28 20:11 ` Andrew Morton
2026-05-29 14:41 ` Stanislav Kinsburskii [this message]
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=ahmliNJiR-R9N4M3@skinsburskii \
--to=skinsburskii@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox