From: Dev Jain <dev.jain@arm.com>
To: akpm@linux-foundation.org, liam@infradead.org, ljs@kernel.org,
jgg@ziepe.ca, leon@kernel.org, david@kernel.org,
shuah@kernel.org
Cc: Dev Jain <dev.jain@arm.com>,
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, ryan.roberts@arm.com,
anshuman.khandual@arm.com, usama.arif@linux.dev
Subject: [PATCH v3 0/2] mm/hmm: A fix and a selftest
Date: Thu, 4 Jun 2026 05:53:04 +0000 [thread overview]
Message-ID: <20260604055308.1947679-1-dev.jain@arm.com> (raw)
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.
---
Applies on mm-unstable (d17fe8a046a2).
v2->v3:
- Use MADV_COLLAPSE, use PAGEMAP_PRESENT
v1->v2:
- Add test
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 | 34 ++++++++++++++++++++++++--
2 files changed, 32 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-04 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 5:53 Dev Jain [this message]
2026-06-04 5:53 ` [PATCH v3 1/2] fs/proc/task_mmu: do not warn on seeing non-migration pmd entry Dev Jain
2026-06-04 5:53 ` [PATCH v3 2/2] selftests/mm/hmm-tests: test pagemap reads of PMD device-private entries Dev Jain
2026-06-05 11:31 ` Lorenzo Stoakes
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=20260604055308.1947679-1-dev.jain@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=balbirs@nvidia.com \
--cc=david@kernel.org \
--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=ljs@kernel.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