From: Andrew Morton <akpm@linux-foundation.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Dev Jain <dev.jain@arm.com>,
liam@infradead.org, jgg@ziepe.ca, leon@kernel.org,
david@kernel.org, shuah@kernel.org, vbabka@kernel.org,
jannh@google.com, pfalcato@suse.de, rppt@kernel.org,
surenb@google.com, mhocko@suse.com, balbirs@nvidia.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com,
stable@vger.kernel.org
Subject: Re: [PATCH] fs/proc/task_mmu: do not warn on seeing non-migration pmd entry
Date: Fri, 29 May 2026 16:36:19 -0700 [thread overview]
Message-ID: <20260529163619.fecd655a4db1f4a6543d5342@linux-foundation.org> (raw)
In-Reply-To: <ahmdJFCw2arBdsd9@lucifer>
On Fri, 29 May 2026 17:45:24 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
> > + /* Exercise pagemap on a PMD device-private entry. */
> > + ret = hmm_read_self_pagemap(buffer->ptr, npages, self->page_size);
> > + ASSERT_EQ(ret, 0);
> > +
> > /* Check what the device read. */
> > for (i = 0, ptr = buffer->mirror; i < size / sizeof(*ptr); ++i)
> > ASSERT_EQ(ptr[i], i);
>
> Thanks for this!
>
> though, hmm it really feels like you maybe want to add this as a test and
> make this a series :)
yes please!
next prev parent reply other threads:[~2026-05-29 23:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 11:17 Dev Jain
2026-05-29 16:45 ` Lorenzo Stoakes
2026-05-29 23:36 ` Andrew Morton [this message]
2026-05-31 19:11 ` David Hildenbrand (Arm)
2026-06-01 4:56 ` Dev Jain
2026-06-01 5:48 ` David Hildenbrand (Arm)
2026-06-02 4:20 ` Oscar Salvador (SUSE)
2026-06-02 4:21 ` Oscar Salvador (SUSE)
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=20260529163619.fecd655a4db1f4a6543d5342@linux-foundation.org \
--to=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=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=stable@vger.kernel.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
Powered by JetHome