From: Petr Vorel <pvorel@suse.cz>
To: Tarun Sahu <tsahu@linux.ibm.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 12/13] Hugetlb: Migrating libhugetlbfs shm-fork
Date: Tue, 3 Jan 2023 19:23:03 +0100 [thread overview]
Message-ID: <Y7Ryhx50EvHpbwI4@pevik> (raw)
In-Reply-To: <20221225154213.84183-13-tsahu@linux.ibm.com>
Hi,
> Migrating the libhugetlbfs/testcases/shm-fork.c test
NOTE: if you're talking about libhugetlbfs [1], the test path is
tests/shm-fork.c (not testcases).
> Test Description: Test shared memory behavior when multiple threads are
> Test shared memory behavior when multiple threads are attached
> to a segment. A segment is created and then children are
> spawned which attach, write, read (verify), and detach from the
> shared memory segment.
> Signed-off-by: Tarun Sahu <tsahu@linux.ibm.com>
> ---
> runtest/hugetlb | 1 +
> testcases/kernel/mem/.gitignore | 1 +
> .../kernel/mem/hugetlb/hugefork/hugefork02.c | 104 ++++++++++++++++++
> 3 files changed, 106 insertions(+)
> create mode 100644 testcases/kernel/mem/hugetlb/hugefork/hugefork02.c
> diff --git a/runtest/hugetlb b/runtest/hugetlb
> index 33fd384b4..348a7dc5f 100644
> --- a/runtest/hugetlb
> +++ b/runtest/hugetlb
> @@ -2,6 +2,7 @@ hugefallocate01 hugefallocate01
> hugefallocate02 hugefallocate02
> hugefork01 hugefork01
> +hugefork02 hugefork02 -P 3 -s 5
You're not define tst_option [2] (you don't even have any code which would hold
these options), therefore passing any of these 2 options will quit the test:
hugefork02: invalid option -- 'P'
Please fix it in next version.
Kind regards,
Petr
[1] https://github.com/libhugetlbfs/libhugetlbfs
[2] https://github.com/linux-test-project/ltp/wiki/C-Test-API#15-test-specific-command-line-options
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-01-03 18:23 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
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 [this message]
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=Y7Ryhx50EvHpbwI4@pevik \
--to=pvorel@suse.cz \
--cc=aneesh.kumar@linux.ibm.com \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=sbhat@linux.ibm.com \
--cc=tsahu@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