From: Tarun Sahu <tsahu@linux.ibm.com>
To: ltp@lists.linux.it
Cc: geetika@linux.ibm.com, sbhat@linux.ibm.com,
aneesh.kumar@linux.ibm.com, vaibhav@linux.ibm.com,
mike.kravetz@oracle.com
Subject: [LTP] [PATCH v4 0/7] Hugetlb:Migrating the libhugetlbfs tests
Date: Wed, 16 Nov 2022 16:55:09 +0530 [thread overview]
Message-ID: <20221116112516.261535-1-tsahu@linux.ibm.com> (raw)
Hi,
This patch series is in continuation to first part [1]
This series include 5 more tests taken from libhugetlbfs.
Background:
Libhugetlbfs is not being maintained actively, and some distro is dropping
support for it. There are some tests that are good for testing hugetlb
functionality in kernel. These patches include tests from libhugetlbfs.
ref:
1. https://lore.kernel.org/all/20221104162511.28658-1-tsahu@linux.ibm.com/
v1 -> v2
1. Fixed comments
v2 -> v3
1. Changed from setjmp/longjmp logic to check/return logic in
hugemmap10.c
2. Added a new patch to create support for custom flags in
tst_creat_unlinked api.
3. Added patch to add safe macros for posix_fadvise call.
4. Updated coding asthetics.
5. Added description along with the line of failure in hugemmap10.c
v3 -> v4
1. Removing redundant access call to check if file already exist.
and removing the retry path, as the case is very rare in PATCH[1/7].
Tarun Sahu (7):
Hugetlb: Migrating libhugetlbfs noresv-reserve-resv-page
Hugetlb: Migrating libhugetlbfs noresv-regarded-as-resv
Hugetlb: Migrating libhugetlbfs private
Hugetlb: Migrating libhugetlbfs readahead_reserve
Hugetlb: Migrating libhugetlbfs readback
Hugetlb: Migrating libhugetlbfs shared
Hugetlb: Migrating libhugetlbfs shm-fork
runtest/hugetlb | 7 +
testcases/kernel/mem/.gitignore | 7 +
.../kernel/mem/hugetlb/hugefork/hugefork02.c | 196 ++++++++++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap27.c | 166 +++++++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap28.c | 107 ++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap29.c | 129 ++++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap30.c | 120 +++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap31.c | 98 +++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap32.c | 104 ++++++++++
9 files changed, 934 insertions(+)
create mode 100644 testcases/kernel/mem/hugetlb/hugefork/hugefork02.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap27.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap28.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap29.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap30.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap31.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap32.c
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-11-16 11:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 11:25 Tarun Sahu [this message]
2022-11-16 11:25 ` [LTP] [PATCH v4 1/7] Hugetlb: Add new argument flags in tst_creat_unlinked Tarun Sahu
2022-11-16 15:17 ` Cyril Hrubis
2022-11-17 7:02 ` Tarun Sahu
2022-11-18 8:27 ` Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 2/7] Hugetlb: Migrating libhugetlbfs counters Tarun Sahu
2022-11-16 15:37 ` Cyril Hrubis
2022-11-16 16:26 ` Tarun Sahu
2022-11-18 14:48 ` Cyril Hrubis
2022-11-18 15:51 ` Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 3/7] Hugetlb: Migrating libhugetlbfs directio Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 4/7] Hugetlb: Safe macro for posix_fadvise call Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 5/7] Hugetlb: Migrating libhugetlbfs fadvise_reserve Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 6/7] Hugetlb: Migrating libhugetlbfs fallocate_align Tarun Sahu
2022-11-16 11:25 ` [LTP] [PATCH v4 7/7] Hugetlb: Migrating libhugetlbfs fallocate_basic 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=20221116112516.261535-1-tsahu@linux.ibm.com \
--to=tsahu@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=mike.kravetz@oracle.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