linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Jinjiang Tu <tujinjiang@huawei.com>,
	akpm@linux-foundation.org, shr@devkernel.io, hannes@cmpxchg.org,
	riel@surriel.com, wangkefeng.wang@huawei.com,
	sunnanyong@huawei.com, linux-mm@kvack.org
Subject: Re: [PATCH v4 3/3] selftest/mm: ksm_functional_tests: extend test case for ksm fork/exec
Date: Thu, 28 Mar 2024 12:33:32 +0100	[thread overview]
Message-ID: <042fae15-5b07-4cab-9818-afbddedc96f2@redhat.com> (raw)
In-Reply-To: <20240328111010.1502191-4-tujinjiang@huawei.com>

On 28.03.24 12:10, Jinjiang Tu wrote:
> This extends test_prctl_fork() and test_prctl_fork_exec() to make sure
> that deduplication really happens, instead of only testing the
> MMF_VM_MERGE_ANY flag is set.
> 
> Suggested-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>
> ---
>   .../selftests/mm/ksm_functional_tests.c       | 49 ++++++++++++++-----
>   1 file changed, 38 insertions(+), 11 deletions(-)
> 
> diff --git a/tools/testing/selftests/mm/ksm_functional_tests.c b/tools/testing/selftests/mm/ksm_functional_tests.c
> index 5462873df84c..2d277620fad2 100644
> --- a/tools/testing/selftests/mm/ksm_functional_tests.c
> +++ b/tools/testing/selftests/mm/ksm_functional_tests.c
> @@ -475,6 +475,36 @@ static void test_prctl(void)
>   	ksft_test_result_pass("Setting/clearing PR_SET_MEMORY_MERGE works\n");
>   }
>   
> +static int test_child_ksm(void)
> +{
> +	const unsigned int size = 2 * MiB;
> +	char *map;
> +
> +	/* Test if KSM is enabled for the process. */
> +	if (prctl(PR_GET_MEMORY_MERGE, 0, 0, 0, 0) != 1)
> +		return -1;
> +
> +	/* Test if merge could really happen. */
> +	map = __mmap_and_merge_range(0xcf, size, PROT_READ | PROT_WRITE, KSM_MERGE_NONE);
> +	if (map == MAP_MERGE_FAIL)
> +		return -2;
> +	else if (map == MAP_MERGE_SKIP)
> +		return -3;
> +
> +	munmap(map, size);
> +	return 0;
> +}
> +
> +static void test_child_ksm_err(int status)

Maybe better "handle_child_ksm_err" because you only call it if status != 0.


Thanks!

Reviewed-by: David Hildenbrand <david@redhat.com>


-- 
Cheers,

David / dhildenb



      reply	other threads:[~2024-03-28 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 11:10 [PATCH v4 0/3] mm/ksm: fix ksm exec support for prctl Jinjiang Tu
2024-03-28 11:10 ` [PATCH v4 1/3] " Jinjiang Tu
2024-03-28 11:10 ` [PATCH v4 2/3] selftest/mm: ksm_functional_tests: refactor mmap_and_merge_range() Jinjiang Tu
2024-03-28 11:30   ` David Hildenbrand
2024-03-28 11:10 ` [PATCH v4 3/3] selftest/mm: ksm_functional_tests: extend test case for ksm fork/exec Jinjiang Tu
2024-03-28 11:33   ` David Hildenbrand [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=042fae15-5b07-4cab-9818-afbddedc96f2@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@surriel.com \
    --cc=shr@devkernel.io \
    --cc=sunnanyong@huawei.com \
    --cc=tujinjiang@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    /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