All of lore.kernel.org
 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 02/13] Hugetlb: Migrating libhugetlbfs mmap-cow
Date: Mon, 26 Dec 2022 13:05:46 +0530	[thread overview]
Message-ID: <20221226073546.md4doiwok4vadq3i@tarunpc> (raw)
In-Reply-To: <CAEemH2dB6RqzSnmN2CH0f1ZtG5sO9T2-RmDSg4cOR2-m-12b7g@mail.gmail.com>

Hi Li,
Thanks for reviewing the patch.
Please find my comments inline.

--skip
> > +static void do_work(int thread, size_t size, int fd)
> > +{
> > +       char *addr;
> > +       size_t i;
> > +       char pattern = thread+65;
> > +
> > +       addr = SAFE_MMAP(NULL, size, PROT_READ|PROT_WRITE, MAP_PRIVATE,
> > fd, 0);
> > +
> > +       tst_res(TINFO, "Thread %d (pid %d): Mapped at address %p",
> > +              thread, getpid(), addr);
> > +
> > +       for (i = 0; i < size; i++)
> > +               memcpy((char *)addr+i, &pattern, 1);
> > +
> > +       if (msync(addr, size, MS_SYNC))
> > +               tst_brk(TBROK|TERRNO, "Thread %d (pid %d): msync() failed",
> > +                               thread, getpid());
> > +
> > +       for (i = 0; i < size; i++)
> > +               if (addr[i] != pattern) {
> > +                       tst_res(TFAIL, "thread %d (pid: %d): Corruption at
> > %p; "
> > +                                  "Got %c, Expected %c", thread, getpid(),
> > +                                  &addr[i], addr[i], pattern);
> > +                       goto cleanup;
> > +               }
> > +       tst_res(TINFO, "Thread %d (pid %d): Pattern verified",
> > +                       thread, getpid());
> >
> 
> Maybe combining the address output with the content of patterns is better?
> 
> i.e.
> 
> --- a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap21.c
> +++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap21.c
> @@ -45,9 +45,6 @@ static void do_work(int thread, size_t size, int fd)
> 
>         addr = SAFE_MMAP(NULL, size, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd,
> 0);
> 
> -       tst_res(TINFO, "Thread %d (pid %d): Mapped at address %p",
> -              thread, getpid(), addr);
> -
>         for (i = 0; i < size; i++)
>                 memcpy((char *)addr+i, &pattern, 1);
> 
> @@ -62,8 +59,8 @@ static void do_work(int thread, size_t size, int fd)
>                                    &addr[i], addr[i], pattern);
>                         goto cleanup;
>                 }
> -       tst_res(TINFO, "Thread %d (pid %d): Pattern verified",
> -                       thread, getpid());
> +       tst_res(TINFO, "Thread %d (pid %d): Pattern %c verified at address
> %p",
> +                       thread, getpid(), pattern, addr);
> 
>  cleanup:
>         SAFE_MUNMAP(addr, size);
> 
In case of failure, this verified comment will not get printed.
In case of success, I dont think it matters to show the content of pattern.
> 
> 
> > +
> > +cleanup:
> > +       SAFE_MUNMAP(addr, size);
> > +       exit(0);
> > +}
> > +
> > +static void run_test(void)
> > +{
> > +       char *addr;
> > +       size_t size, itr;
> > +       int i, pid;
> > +       pid_t *wait_list;
> > +
> > +       wait_list = SAFE_MALLOC(THREADS * sizeof(pid_t));
> > +       size = (NR_HUGEPAGES / (THREADS+1)) * hpage_size;
> > +
> > +
> > +       /* First, mmap the file with MAP_SHARED and fill with data
> > +        * If this is not done, then the fault handler will not be
> > +        * called in the kernel since private mappings will be
> > +        * created for the children at prefault time.
> > +        */
> > +       addr = SAFE_MMAP(NULL, size, PROT_READ|PROT_WRITE, MAP_SHARED, fd,
> > 0);
> > +
> > +       for (itr = 0; itr < size; itr += 8)
> > +               memcpy(addr+itr, "deadbeef", 8);
> > +
> > +       for (i = 0; i < THREADS; i++) {
> > +               pid = SAFE_FORK();
> > +
> > +               if (pid == 0)
> > +                       do_work(i, size, fd);
> > +
> > +               wait_list[i] = pid;
> > +       }
> > +       tst_reap_children();
> > +
> > +       SAFE_MUNMAP(addr, size);
> > +       free(wait_list);
> > +       tst_res(TPASS, "mmap COW working as expected.");
> > +}
> > +
> > +static void setup(void)
> > +{
> > +       hpage_size = SAFE_READ_MEMINFO(MEMINFO_HPAGE_SIZE)*1024;
> >
> 
> We do have a dedicated function named tst_get_hugepage_size();
> could be used for getting huge page size.
Oh right! I could have used it in all other previous tests too.
Thanks for pointing this, Will take care of it in next revision.
> 
> The rest part looks good to me.
> 
> Reviewed-by: Li Wang <liwang@redhat.com>
> 
> 
> 
> > +       fd = tst_creat_unlinked(MNTPOINT, 0);
> > +}
> > +
> > +static void cleanup(void)
> > +{
> > +       if (fd >= 1)
> > +               SAFE_CLOSE(fd);
> > +}
> > +
> > +static struct tst_test test = {
> > +       .needs_root = 1,
> > +       .mntpoint = MNTPOINT,
> > +       .needs_hugetlbfs = 1,
> > +       .needs_tmpdir = 1,
> > +       .forks_child = 1,
> > +       .setup = setup,
> > +       .cleanup = cleanup,
> > +       .test_all = run_test,
> > +       .hugepages = {NR_HUGEPAGES, TST_NEEDS},
> > +};
> > --
> > 2.31.1
> >
> >
> 
> -- 
> 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-26  7:55 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 [this message]
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
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=20221226073546.md4doiwok4vadq3i@tarunpc \
    --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 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.