public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Tarun Sahu <tsahu@linux.ibm.com>
To: Li Wang <liwang@redhat.com>
Cc: sbhat@linux.ibm.com, aneesh.kumar@linux.ibm.com,
	geetika@linux.ibm.com, vaibhav@linux.ibm.com,
	rpalethorpe@suse.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 06/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-normal-near-huge
Date: Fri, 30 Dec 2022 00:36:31 +0530	[thread overview]
Message-ID: <878riqghc8.fsf@linux.ibm.com> (raw)
In-Reply-To: <87tu1gogg9.fsf@linux.ibm.com>

Hi,


Tarun Sahu <tsahu@linux.ibm.com> writes:

> Hi Li,
> Thanks for reviewing the patch.
> I will update it in next revision.
>
> --skip
>>> +static int do_readback(void *p, size_t size, const char *stage)
>>> +{
>>> +       unsigned int *q = p;
>>> +       size_t i;
>>> +
>>> +       tst_res(TINFO, "%s(%p, 0x%lx, \"%s\")", __func__, p,
>>> +              (unsigned long)size, stage);
>>> +
>>> +       for (i = 0; i < (size / sizeof(*q)); i++)
>>> +               q[i] = RANDOM_CONSTANT ^ i;
>>> +
>>> +       for (i = 0; i < (size / sizeof(*q)); i++) {
>>> +               if (q[i] != (RANDOM_CONSTANT ^ i)) {
>>> +                       tst_res(TFAIL, "Stage \"%s\": Mismatch at offset
>>> 0x%lx: 0x%x "
>>> +                                       "instead of 0x%lx", stage, i,
>>> q[i], RANDOM_CONSTANT ^ i);
>>> +                       return -1;
>>> +               }
>>> +       }
>>> +       return 0;
>>> +}
>>> +
>>> +static int do_remap(void *target)
>>> +{
>>> +       void *a, *b;
>>> +       int ret;
>>> +
>>> +       a = SAFE_MMAP(NULL, page_size, PROT_READ|PROT_WRITE,
>>> +                 MAP_SHARED|MAP_ANONYMOUS, -1, 0);
>>> +
>>> +       ret = do_readback(a, page_size, "base normal");
>>> +       if (ret)
>>> +               goto cleanup;
>>> +       b = mremap(a, page_size, page_size, MREMAP_MAYMOVE | MREMAP_FIXED,
>>> +                  target);
>>> +
>>> +       if (b != MAP_FAILED) {
>>> +               do_readback(b, page_size, "remapped");
>>> +               a = b;
>>> +       } else
>>> +               tst_res(TINFO|TERRNO, "mremap(MAYMOVE|FIXED) disallowed");
>>> +
>>> +cleanup:
>>> +       SAFE_MUNMAP(a, page_size);
>>> +       return ret;
>>> +}
>>>
>>
>> Those two functions do_readback() and do_remap() are
>> copy&past from hugemmap2[4|5].c, what about extracting
>> them into a common header file(tst_hugetlb.h or mem.h) for
>> easy reusing?
>>
> ok, I think, hugetlb.h/.c will be better place to keep them.
>
These two functions are very specific to tests (specially the do_remap).
Also, they use values that are defined only inside the test.
Though do_readback is more general which can be put in hugetlb.h/c.

WDYT?
>> And I also noticed other tests (hugemmap27) using the same
>> macro mem barrier(), it'd be great to define it in a header file.
>>
> ok.
>>
>> -- 
>> Regards,
>> Li Wang
>>
>> -- 
>> Mailing list info: https://lists.linux.it/listinfo/ltp

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-12-29 19:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 15:42 [LTP] [PATCH 0/13][PART 4] Hugetlb:Migrating the libhugetlbfs tests Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 01/13] Hugetlb: Migrating libhugetlbfs mlock Tarun Sahu
2022-12-26  4:48   ` Li Wang
2022-12-26  9:39     ` Tarun Sahu
2022-12-26  9:48       ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 02/13] Hugetlb: Migrating libhugetlbfs mmap-cow Tarun Sahu
2022-12-26  6:57   ` Li Wang
2022-12-26  7:35     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 03/13] Hugetlb: Migrating libhugetlbfs mmap-gettest Tarun Sahu
2022-12-26  7:33   ` Li Wang
2022-12-26  9:41     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 04/13] Hugetlb: Migrating libhugetlbfs mprotect Tarun Sahu
2022-12-27  5:48   ` Li Wang
2022-12-27 16:00     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 05/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-huge-near-normal Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 06/13] Hugetlb: Migrating libhugetlbfs mremap-fixed-normal-near-huge Tarun Sahu
2022-12-27  6:31   ` Li Wang
2022-12-27 18:21     ` Tarun Sahu
2022-12-29 19:06       ` Tarun Sahu [this message]
2022-12-30  3:49         ` Li Wang
2022-12-31  5:08           ` Tarun Sahu
2023-01-03  3:06             ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 07/13] Hugetlb: Migrating libhugetlbfs noresv-reserve-resv-page Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 08/13] Hugetlb: Migrating libhugetlbfs noresv-regarded-as-resv Tarun Sahu
2022-12-27  6:47   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 09/13] Hugetlb: Migrating libhugetlbfs private Tarun Sahu
2022-12-27  6:56   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 10/13] Hugetlb: Migrating libhugetlbfs readahead_reserve Tarun Sahu
2022-12-27  7:05   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 11/13] Hugetlb: Migrating libhugetlbfs shared Tarun Sahu
2022-12-27  7:08   ` Li Wang
2022-12-25 15:42 ` [LTP] [PATCH 12/13] Hugetlb: Migrating libhugetlbfs shm-fork Tarun Sahu
2022-12-28  3:15   ` Li Wang
2023-01-03 18:23   ` Petr Vorel
2023-01-04 17:59     ` Tarun Sahu
2022-12-25 15:42 ` [LTP] [PATCH 13/13] Hugetlb: Migrating libhugetlbfs mremap-expand-slice-collision Tarun Sahu

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=878riqghc8.fsf@linux.ibm.com \
    --to=tsahu@linux.ibm.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=geetika@linux.ibm.com \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.com \
    --cc=sbhat@linux.ibm.com \
    --cc=vaibhav@linux.ibm.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