From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
david@redhat.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
riel@surriel.com, harry.yoo@oracle.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org
Subject: Re: [Patch v3 0/2] assert rmap behaves as expected
Date: Mon, 18 Aug 2025 06:40:26 +0000 [thread overview]
Message-ID: <20250818064026.htixfallwid3cdf4@master> (raw)
In-Reply-To: <20250817200642.c3ca3c89832fd9e0cb5117f4@linux-foundation.org>
On Sun, Aug 17, 2025 at 08:06:42PM -0700, Andrew Morton wrote:
>On Mon, 18 Aug 2025 02:29:03 +0000 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> As David suggested, currently we don't have a high level test case to
>> verify the behavior of rmap. This patch set introduce the verification
>> on rmap by migration.
>
>I'm seeing many rejects here, so please redo against tomorrow's mm-new?
>
Sure.
>Also, seeing "assert" in the changelogs was a little surprising. The
>term "assert" made me expect to see assertions, such as VM_BUG_ON().
>Perhaps "test that" would be clearer.
Will update it.
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2025-08-18 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 2:29 [Patch v3 0/2] assert rmap behaves as expected Wei Yang
2025-08-18 2:29 ` [Patch v3 1/2] selftests/mm: put general ksm operation into vm_util Wei Yang
2025-08-18 2:29 ` [Patch v3 2/2] selftests/mm: assert rmap behave as expected Wei Yang
2025-08-18 3:06 ` [Patch v3 0/2] assert rmap behaves " Andrew Morton
2025-08-18 6:40 ` Wei Yang [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=20250818064026.htixfallwid3cdf4@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=rppt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.