From: David Hildenbrand <david@redhat.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
riel@surriel.com, Liam.Howlett@oracle.com, vbabka@suse.cz,
harry.yoo@oracle.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org
Subject: Re: [RFC Patch 2/2] selftests/mm: assert rmap behave as expected
Date: Fri, 11 Jul 2025 17:39:39 +0200 [thread overview]
Message-ID: <2ee1d2ca-94c5-4c27-b2dc-bcea2b710dcf@redhat.com> (raw)
In-Reply-To: <20250604083441.hilkdzlxmxygivvt@master>
On 04.06.25 10:34, Wei Yang wrote:
> On Wed, Jun 04, 2025 at 08:21:45AM +0000, Wei Yang wrote:
> [...]
>> +int try_to_move_page(char *region)
>> +{
>> + int ret;
>> + int node;
>> + int status = 0;
>> +
>> + ksft_print_msg("worker %d move_pages of content: %.15s\n", getpid(), region);
>
> One thing confused me here.
>
> If I don't access region here, the following move_pages() would report
> -ENOENT occationally. The reason is do_pages_stat_array() ->
> folio_walk_start() returns NULL.
Right, the pages were not faulted in. The man page mentions that as
"-ENOENT: The page is not present."
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-11 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:21 [RFC Patch 0/2] selftests/mm: assert rmap behave as expected Wei Yang
2025-06-04 8:21 ` [RFC Patch 1/2] selftests/mm: put general ksm operation into vm_util Wei Yang
2025-07-11 15:37 ` David Hildenbrand
2025-07-14 2:45 ` Wei Yang
2025-06-04 8:21 ` [RFC Patch 2/2] selftests/mm: assert rmap behave as expected Wei Yang
2025-06-04 8:34 ` Wei Yang
2025-07-11 15:39 ` David Hildenbrand [this message]
2025-07-14 14:42 ` Wei Yang
2025-07-14 14:45 ` David Hildenbrand
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=2ee1d2ca-94c5-4c27-b2dc-bcea2b710dcf@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=harry.yoo@oracle.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=richard.weiyang@gmail.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).