linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: Deduplicate test names in madv_populate
Date: Thu, 22 May 2025 14:59:45 -0400	[thread overview]
Message-ID: <aboathzpwqqgy5j3jw53cubmrtlzelazdysksqnfb5niruto43@ptubjb5ptakg> (raw)
In-Reply-To: <20250522-selftests-mm-madv-populate-dedupe-v1-1-fd1dedd79b4b@kernel.org>

* Mark Brown <broonie@kernel.org> [250522 12:30]:
> The madv_populate selftest has some repetitive code for several different
> cases that it covers, included repeated test names used in ksft_test_result()
> reports. This causes problems for automation, the test name is used to both
> track the test between runs and distinguish between multiple tests within
> the same run. Fix this by tweaking the messages with duplication to be more
> specific about the contexts they're in.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>

Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>

> ---
>  tools/testing/selftests/mm/madv_populate.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/tools/testing/selftests/mm/madv_populate.c b/tools/testing/selftests/mm/madv_populate.c
> index ef7d911da13e..b6fabd5c27ed 100644
> --- a/tools/testing/selftests/mm/madv_populate.c
> +++ b/tools/testing/selftests/mm/madv_populate.c
> @@ -172,12 +172,12 @@ static void test_populate_read(void)
>  	if (addr == MAP_FAILED)
>  		ksft_exit_fail_msg("mmap failed\n");
>  	ksft_test_result(range_is_not_populated(addr, SIZE),
> -			 "range initially not populated\n");
> +			 "read range initially not populated\n");
>  
>  	ret = madvise(addr, SIZE, MADV_POPULATE_READ);
>  	ksft_test_result(!ret, "MADV_POPULATE_READ\n");
>  	ksft_test_result(range_is_populated(addr, SIZE),
> -			 "range is populated\n");
> +			 "read range is populated\n");
>  
>  	munmap(addr, SIZE);
>  }
> @@ -194,12 +194,12 @@ static void test_populate_write(void)
>  	if (addr == MAP_FAILED)
>  		ksft_exit_fail_msg("mmap failed\n");
>  	ksft_test_result(range_is_not_populated(addr, SIZE),
> -			 "range initially not populated\n");
> +			 "write range initially not populated\n");
>  
>  	ret = madvise(addr, SIZE, MADV_POPULATE_WRITE);
>  	ksft_test_result(!ret, "MADV_POPULATE_WRITE\n");
>  	ksft_test_result(range_is_populated(addr, SIZE),
> -			 "range is populated\n");
> +			 "write range is populated\n");
>  
>  	munmap(addr, SIZE);
>  }
> @@ -247,19 +247,19 @@ static void test_softdirty(void)
>  	/* Clear any softdirty bits. */
>  	clear_softdirty();
>  	ksft_test_result(range_is_not_softdirty(addr, SIZE),
> -			 "range is not softdirty\n");
> +			 "cleared range is not softdirty\n");
>  
>  	/* Populating READ should set softdirty. */
>  	ret = madvise(addr, SIZE, MADV_POPULATE_READ);
> -	ksft_test_result(!ret, "MADV_POPULATE_READ\n");
> +	ksft_test_result(!ret, "softdirty MADV_POPULATE_READ\n");
>  	ksft_test_result(range_is_not_softdirty(addr, SIZE),
> -			 "range is not softdirty\n");
> +			 "range is not softdirty after MADV_POPULATE_READ\n");
>  
>  	/* Populating WRITE should set softdirty. */
>  	ret = madvise(addr, SIZE, MADV_POPULATE_WRITE);
> -	ksft_test_result(!ret, "MADV_POPULATE_WRITE\n");
> +	ksft_test_result(!ret, "softdirty MADV_POPULATE_WRITE\n");
>  	ksft_test_result(range_is_softdirty(addr, SIZE),
> -			 "range is softdirty\n");
> +			 "range is softdirty after MADV_POPULATE_WRITE \n");
>  
>  	munmap(addr, SIZE);
>  }
> 
> ---
> base-commit: a5806cd506af5a7c19bcd596e4708b5c464bfd21
> change-id: 20250521-selftests-mm-madv-populate-dedupe-95faf16c3c8f
> 
> Best regards,
> -- 
> Mark Brown <broonie@kernel.org>
> 
> 


  reply	other threads:[~2025-05-22 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 16:29 Mark Brown
2025-05-22 18:59 ` Liam R. Howlett [this message]
2025-05-26 12:57 ` 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=aboathzpwqqgy5j3jw53cubmrtlzelazdysksqnfb5niruto43@ptubjb5ptakg \
    --to=liam.howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    /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