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 v3 0/7] Hugetlb:Migrating the libhugetlbfs tests
Date: Tue, 15 Nov 2022 12:37:45 +0530 [thread overview]
Message-ID: <20221115070752.244461-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.
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
Tarun Sahu (7):
Hugetlb: Add new argument flags in tst_creat_unlinked
Hugetlb: Migrating libhugetlbfs counters
Hugetlb: Migrating libhugetlbfs directio
Hugetlb: Safe macro for posix_fadvise call
Hugetlb: Migrating libhugetlbfs fadvise_reserve
Hugetlb: Migrating libhugetlbfs fallocate_align
Hugetlb: Migrating libhugetlbfs fallocate_basic
include/tst_safe_macros.h | 17 +
include/tst_test.h | 2 +-
lib/tst_test.c | 22 +-
runtest/hugetlb | 6 +
testcases/kernel/mem/.gitignore | 5 +
.../kernel/mem/hugetlb/hugefallocate/Makefile | 10 +
.../hugetlb/hugefallocate/hugefallocate01.c | 169 +++++++
.../hugetlb/hugefallocate/hugefallocate02.c | 90 ++++
.../kernel/mem/hugetlb/hugemmap/hugemmap07.c | 2 +-
.../kernel/mem/hugetlb/hugemmap/hugemmap08.c | 2 +-
.../kernel/mem/hugetlb/hugemmap/hugemmap09.c | 2 +-
.../kernel/mem/hugetlb/hugemmap/hugemmap10.c | 462 ++++++++++++++++++
.../kernel/mem/hugetlb/hugemmap/hugemmap11.c | 87 ++++
.../kernel/mem/hugetlb/hugemmap/hugemmap12.c | 84 ++++
14 files changed, 951 insertions(+), 9 deletions(-)
create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/Makefile
create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate01.c
create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate02.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c
create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c
--
2.31.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2022-11-15 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 7:07 Tarun Sahu [this message]
2022-11-15 7:07 ` [LTP] [PATCH v3 1/7] Hugetlb: Add new argument flags in tst_creat_unlinked Tarun Sahu
2022-11-16 5:32 ` Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 2/7] Hugetlb: Migrating libhugetlbfs counters Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 3/7] Hugetlb: Migrating libhugetlbfs directio Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 4/7] Hugetlb: Safe macro for posix_fadvise call Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 5/7] Hugetlb: Migrating libhugetlbfs fadvise_reserve Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 6/7] Hugetlb: Migrating libhugetlbfs fallocate_align Tarun Sahu
2022-11-15 7:07 ` [LTP] [PATCH v3 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=20221115070752.244461-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