From: Lorenzo Stoakes <ljs@kernel.org>
To: Dev Jain <dev.jain@arm.com>
Cc: akpm@linux-foundation.org, liam@infradead.org, jgg@ziepe.ca,
leon@kernel.org, david@kernel.org, shuah@kernel.org,
vbabka@kernel.org, jannh@google.com, pfalcato@suse.de,
balbirs@nvidia.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
linux-kselftest@vger.kernel.org, usama.arif@linux.dev,
ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v2 0/2] mm/hmm: A fix and a selftest
Date: Mon, 1 Jun 2026 09:33:57 +0100 [thread overview]
Message-ID: <ah1D1Qs4fPnO5sH2@lucifer> (raw)
In-Reply-To: <20260530085413.1270139-1-dev.jain@arm.com>
On Sat, May 30, 2026 at 08:54:10AM +0000, Dev Jain wrote:
> Patch 1 fixes a stale warning present from the time when only migration
> softleaf entries were supported at the PMD level.
>
> Patch 2 adds some code into hmm-tests.c which exercises the pagemap path
> for PMD device-private entries.
Thanks!
FYI running the HMM tests locally I ran into a nasty issue that I sent a patch
for [0]!
[0]: https://lore.kernel.org/linux-mm/20260601083044.57132-1-ljs@kernel.org/
Cheers, Lorenzo
>
> ---
> Applies on mm-unstable (404fb4f38e8f).
>
> Dev Jain (2):
> fs/proc/task_mmu: do not warn on seeing non-migration pmd entry
> selftests/mm/hmm-tests: test pagemap reads of PMD device-private
> entries
>
> fs/proc/task_mmu.c | 1 -
> tools/testing/selftests/mm/hmm-tests.c | 29 ++++++++++++++++++++++++++
> 2 files changed, 29 insertions(+), 1 deletion(-)
>
> --
> 2.43.0
>
prev parent reply other threads:[~2026-06-01 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 8:54 Dev Jain
2026-05-30 8:54 ` [PATCH v2 1/2] fs/proc/task_mmu: do not warn on seeing non-migration pmd entry Dev Jain
2026-05-31 23:39 ` Balbir Singh
2026-06-01 8:36 ` Lorenzo Stoakes
2026-05-30 8:54 ` [PATCH v2 2/2] selftests/mm/hmm-tests: test pagemap reads of PMD device-private entries Dev Jain
2026-06-01 0:09 ` Balbir Singh
2026-06-01 5:10 ` Dev Jain
2026-06-01 8:35 ` Lorenzo Stoakes
2026-06-01 9:14 ` Dev Jain
2026-05-31 19:24 ` [PATCH v2 0/2] mm/hmm: A fix and a selftest Andrew Morton
2026-05-31 19:49 ` David Hildenbrand (Arm)
2026-06-01 5:11 ` Dev Jain
2026-06-01 8:33 ` Lorenzo Stoakes [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=ah1D1Qs4fPnO5sH2@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=balbirs@nvidia.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--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
Powered by JetHome