linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: xu xin <xu.xin.sc@gmail.com>
To: david@redhat.com
Cc: akpm@linux-foundation.org, imbrenda@linux.ibm.com,
	jiang.xuexin@zte.com.cn, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com,
	xu.xin16@zte.com.cn, yang.yang29@zte.com.cn
Subject: Re: [PATCH v9 5/5] selftest: add a testcase of ksm zero pages
Date: Wed, 24 May 2023 17:38:36 +0800	[thread overview]
Message-ID: <20230524093836.21038-1-xu.xin16@zte.com.cn> (raw)
In-Reply-To: <84c00f9d-0b83-e4a2-de6f-617cf23b6444@redhat.com>

>> +	if (write(ksm_use_zero_pages_fd, "1", 1) != 1) {
>> +		ksft_test_result_skip("write \"/sys/kernel/mm/ksm/use_zero_pages\" failed\n");
>> +		return;
>> +	}
>
>I realize that this test will fail if there is any other process in the system that has KSM
>Enabled with a suitable page filled with zeroes ... maybe instead of checking the global
>KSM zeropages, check the per-mm ones instead? That should be better

Emmm, yes. It makes sense. I'll do it per-mm in next-version.

>You could do something like the following on top (I recall you had some kind of COW
>tests previously, this should be a simplified version of it):
>

Ok. Thank you.

>diff --git a/tools/testing/selftests/mm/ksm_functional_tests.c b/tools/testing/selftests/mm/ksm_functional_tests.c
>index ea060c683c80..160675a4e3d2 100644
>--- a/tools/testing/selftests/mm/ksm_functional_tests.c
>+++ b/tools/testing/selftests/mm/ksm_functional_tests.c
>@@ -182,6 +182,7 @@ static void test_unmerge(void)
>  static void test_unmerge_zero_pages(void)
>  {
>  	const unsigned int size = 2 * MiB;
>+	unsigned int offs;
>  	char *map;
>  	unsigned long pages_expected;
>  
>@@ -225,8 +226,18 @@ static void test_unmerge_zero_pages(void)
>  		goto unmap;
>  	}
>  
>+	/* Trigger unmerging of the other half by writing to the pages. */
>+	for (offs = size / 2; offs < size; offs += pagesize)
>+		*((unsigned int *)&map[offs]) = offs;
>+
>+	/* We should have no zeropages remaining. */
>+	if (get_ksm_zero_pages()) {
>+		ksft_test_result_fail("'ksm_zero_pages' updated after write fault\n");
>+		goto unmap;
>+	}
>+
>  	/* Check if ksm zero pages are really unmerged */
>-	ksft_test_result(!range_maps_duplicates(map, size / 2),
>+	ksft_test_result(!range_maps_duplicates(map, size),
>  				"KSM zero pages were unmerged\n");
>  unmap:
>  	munmap(map, size);


  reply	other threads:[~2023-05-24  9:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  5:51 [PATCH v9 0/5] ksm: support tracking KSM-placed zero-pages yang.yang29
     [not found] ` <20230524055711.20387-1-yang.yang29@zte.com.cn>
2023-05-24  7:10   ` [PATCH v9 1/5] ksm: support unsharing KSM-placed zero pages David Hildenbrand
     [not found] ` <20230524055752.20449-1-yang.yang29@zte.com.cn>
2023-05-24  7:23   ` [PATCH v9 2/5] ksm: count all zero pages placed by KSM David Hildenbrand
2023-05-24  7:55     ` xu xin
2023-05-24  8:27       ` David Hildenbrand
     [not found] ` <20230524055800.20498-1-yang.yang29@zte.com.cn>
2023-05-24  7:24   ` [PATCH v9 3/5] ksm: add ksm zero pages for each process David Hildenbrand
2023-05-25  3:36   ` kernel test robot
2023-05-25  6:56   ` kernel test robot
2023-05-29  1:48     ` xu xin
     [not found] ` <20230524055851.20565-1-yang.yang29@zte.com.cn>
2023-05-24  7:25   ` [PATCH v9 4/5] ksm: consider KSM-placed zeropages when calculating KSM profit David Hildenbrand
     [not found] ` <20230524055906.20614-1-yang.yang29@zte.com.cn>
2023-05-24  9:11   ` [PATCH v9 5/5] selftest: add a testcase of ksm zero pages David Hildenbrand
2023-05-24  9:38     ` xu xin [this message]
2023-05-24  9:12 ` [PATCH v9 0/5] ksm: support tracking KSM-placed zero-pages 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=20230524093836.21038-1-xu.xin16@zte.com.cn \
    --to=xu.xin.sc@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=jiang.xuexin@zte.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ran.xiaokai@zte.com.cn \
    --cc=xu.xin16@zte.com.cn \
    --cc=yang.yang29@zte.com.cn \
    /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