All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donet Tom <donettom@linux.ibm.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	David Hildenbrand <david@redhat.com>, Dev Jain <dev.jain@arm.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Zi Yan <ziy@nvidia.com>
Subject: Re: [Patch v2] selftests/mm: do check_huge_anon() with a number been passed in
Date: Mon, 11 Aug 2025 07:18:38 +0530	[thread overview]
Message-ID: <9fbc3206-3bbb-4697-959f-e413c4d3580a@linux.ibm.com> (raw)
In-Reply-To: <20250811005359.v2t75i4nhdyj5ev7@master>


On 8/11/25 6:23 AM, Wei Yang wrote:
> On Sun, Aug 10, 2025 at 07:07:47PM +0530, Donet Tom wrote:
>> On 8/10/25 1:12 AM, Wei Yang wrote:
>>> Currently it hard codes the number of hugepage to check for
>>> check_huge_anon(), but it would be more reasonable to do the check based
>>> on a number passed in.
>>>
>>> Pass in the hugepage number and do the check based on it.
>>>
>>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>>> Cc: Baolin Wang <baolin.wang@linux.alibaba.com>
>>> Cc: Donet Tom <donettom@linux.ibm.com>
>>> Cc: David Hildenbrand <david@redhat.com>
>>> Cc: Dev Jain <dev.jain@arm.com>
>>> Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>>> Cc: Zi Yan <ziy@nvidia.com>
>>>
>>> ---
>>> v2:
>>>     * use mm-new
>>>     * add back nr_hpages which is removed by an early commit
>>>     * adjust the change log a little
>>>     * drop RB and resend
>>> ---
>>>    tools/testing/selftests/mm/split_huge_page_test.c | 6 +++---
>>>    1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/tools/testing/selftests/mm/split_huge_page_test.c b/tools/testing/selftests/mm/split_huge_page_test.c
>>> index 5ab488fab1cd..63ac82f0b9e0 100644
>>> --- a/tools/testing/selftests/mm/split_huge_page_test.c
>>> +++ b/tools/testing/selftests/mm/split_huge_page_test.c
>>> @@ -105,12 +105,12 @@ static char *allocate_zero_filled_hugepage(size_t len)
>>>    	return result;
>>>    }
>>> -static void verify_rss_anon_split_huge_page_all_zeroes(char *one_page, size_t len)
>>> +static void verify_rss_anon_split_huge_page_all_zeroes(char *one_page, int nr_hpages, size_t len)
>>
>> We are re-adding this argument because nr_hpages should be the same in both
>> split_pmd_zero_pages and verify_rss_anon_split_huge_page_all_zeroes,
>> correct? I was just wondering — since the value is currently hardcoded
>> in both functions, would it be preferable to pass it as an argument,
>> or keep it hardcoded, What benefit do we gain by re-adding this argument?
>>
> Thanks for your comment.
>
> It looks the correct way to do so.

Thank you for the clarification

LGTM

Reviewed by: Donet Tom <donettom@linux.ibm.com>

>

  reply	other threads:[~2025-08-11  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-09 19:42 [Patch v2] selftests/mm: do check_huge_anon() with a number been passed in Wei Yang
2025-08-10 13:37 ` Donet Tom
2025-08-11  0:53   ` Wei Yang
2025-08-11  1:48     ` Donet Tom [this message]
2025-08-11  5:58 ` Baolin Wang
2025-08-11  8:00 ` David Hildenbrand
2025-08-11 18:42 ` Zi Yan
2025-08-11 20:08 ` Vishal Moola (Oracle)
2025-08-12  2:26 ` wang lian

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=9fbc3206-3bbb-4697-959f-e413c4d3580a@linux.ibm.com \
    --to=donettom@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=dev.jain@arm.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=richard.weiyang@gmail.com \
    --cc=ziy@nvidia.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 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.