From: Wei Yang <richard.weiyang@gmail.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
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: Wed, 4 Jun 2025 08:34:41 +0000 [thread overview]
Message-ID: <20250604083441.hilkdzlxmxygivvt@master> (raw)
In-Reply-To: <20250604082145.13800-3-richard.weiyang@gmail.com>
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.
Not sure which part I missed.
>+
>+ ret = move_pages(0, 1, (void **)®ion, NULL, &status, MPOL_MF_MOVE_ALL);
>+ if (ret != 0)
>+ return FAIL_ON_WORK;
>+
>+ /* Pick up a different target node */
>+ for (node = 0; node <= numa_max_node(); node++) {
>+ if (numa_bitmask_isbitset(numa_all_nodes_ptr, node) && node != status)
>+ break;
>+ }
>+
>+ if (node > numa_max_node()) {
>+ ksft_print_msg("Couldn't find available numa node for testing\n");
>+ return FAIL_ON_WORK;
>+ }
>+
>+ ret = move_pages(0, 1, (void **)®ion, &node, &status, MPOL_MF_MOVE_ALL);
>+ if (ret != 0)
>+ return FAIL_ON_WORK;
>+
>+ return 0;
>+}
>+
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-06-04 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 8:21 [RFC Patch 0/2] " 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 [this message]
2025-07-11 15:39 ` David Hildenbrand
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=20250604083441.hilkdzlxmxygivvt@master \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.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