linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Donet Tom <donettom@linux.ibm.com>
To: Mark Brown <broonie@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>
Cc: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	Muhammad Usama Anjum <usama.anjum@collabora.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftest: hugetlb_dio: Fix test naming
Date: Thu, 28 Nov 2024 10:46:56 +0530	[thread overview]
Message-ID: <8174031c-b9b1-4e32-806e-28f1b2c1dee0@linux.ibm.com> (raw)
In-Reply-To: <20241127-kselftest-mm-hugetlb-dio-names-v1-1-22aab01bf550@kernel.org>


On 11/27/24 21:44, Mark Brown wrote:
> The string logged when a test passes or fails is used by the selftest
> framework to identify which test is being reported. The hugetlb_dio test
> not only uses the same strings for every test that is run but it also uses
> different strings for test passes and failures which means that test
> automation is unable to follow what the test is doing at all.
>
> Pull the existing duplicated logging of the number of free huge pages
> before and after the test out of the conditional and replace that and the
> logging of the result with a single ksft_print_result() which incorporates
> the parameters passed into the test into the output.
>
> Fixes: fae1980347bf ("selftests: hugetlb_dio: fixup check for initial conditions to skip in the start")
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>   tools/testing/selftests/mm/hugetlb_dio.c | 14 +++++---------
>   1 file changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/hugetlb_dio.c b/tools/testing/selftests/mm/hugetlb_dio.c
> index 432d5af15e66b7d6cac0273fb244d6696d7c9ddc..db63abe5ee5e85ff7795d3ea176c3ac47184bf4f 100644
> --- a/tools/testing/selftests/mm/hugetlb_dio.c
> +++ b/tools/testing/selftests/mm/hugetlb_dio.c
> @@ -76,19 +76,15 @@ void run_dio_using_hugetlb(unsigned int start_off, unsigned int end_off)
>   	/* Get the free huge pages after unmap*/
>   	free_hpage_a = get_free_hugepages();
>   
> +	ksft_print_msg("No. Free pages before allocation : %d\n", free_hpage_b);
> +	ksft_print_msg("No. Free pages after munmap : %d\n", free_hpage_a);
> +
>   	/*
>   	 * If the no. of free hugepages before allocation and after unmap does
>   	 * not match - that means there could still be a page which is pinned.
>   	 */
> -	if (free_hpage_a != free_hpage_b) {
> -		ksft_print_msg("No. Free pages before allocation : %d\n", free_hpage_b);
> -		ksft_print_msg("No. Free pages after munmap : %d\n", free_hpage_a);
> -		ksft_test_result_fail(": Huge pages not freed!\n");
> -	} else {
> -		ksft_print_msg("No. Free pages before allocation : %d\n", free_hpage_b);
> -		ksft_print_msg("No. Free pages after munmap : %d\n", free_hpage_a);
> -		ksft_test_result_pass(": Huge pages freed successfully !\n");
> -	}
> +	ksft_test_result(free_hpage_a == free_hpage_b,
> +			 "free huge pages from %u-%u\n", start_off, end_off);

Hi Mark

This test allocates a hugetlb buffer and adjusts the start and end offsets of the buffer based
on|start_off|  and|end_off|. The adjusted buffer is then used for Direct I/O (DIO). If I understand
correctly,|start_off|  and|end_off|  are not free huge pages but rather DIO buffer offsets. Should we
change this message to "Hugetlb DIO buffer offset"?

Thanks
Donet

>   }
>   
>   int main(void)
>
> ---
> base-commit: 6f3d2b5299b0a8bcb8a9405a8d3fceb24f79c4f0
> change-id: 20241127-kselftest-mm-hugetlb-dio-names-1ebccbe8183d
>
> Best regards,


  reply	other threads:[~2024-11-28  5:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27 16:14 Mark Brown
2024-11-28  5:16 ` Donet Tom [this message]
2024-11-28 12:44   ` Mark Brown
2024-11-28 12:58     ` Donet Tom
2024-11-28  7:14 ` Muhammad Usama Anjum

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=8174031c-b9b1-4e32-806e-28f1b2c1dee0@linux.ibm.com \
    --to=donettom@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ritesh.list@gmail.com \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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