Hugetlb:Migrating the libhugetlbfs tests
v2 cover Hugetlb:Migrating the libhugetlbfs tests
Hi,
This patch series is in continution to first part [1]. This series include 5 more tests taken from libhugetlbfs.
ref:
1. https://lore.kernel.org/all/[email protected]/
v1 -> v2
1. Fixed comments
Tarun Sahu (5):
Hugetlb: Migrating libhugetlbfs counters
Hugetlb: Migrating libhugetlbfs directio
Hugetlb: Migrating libhugetlbfs fadvise_reserve
Hugetlb: Migrating libhugetlbfs fallocate_align
Hugetlb: Migrating libhugetlbfs fallocate_basic
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/hugemmap10.c | 438 ++++++++++++++++++ .../kernel/mem/hugetlb/hugemmap/hugemmap11.c | 87 ++++ .../kernel/mem/hugetlb/hugemmap/hugemmap12.c | 93 ++++ 8 files changed, 898 insertions(+) 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
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp
PATCH v2 1/5 Hugetlb: Migrating libhugetlbfs counters
Migrating the libhugetlbfs/testcases/counters.c test
Test Description: This Test perform mmap and unmap and write operation on hugetlb file based mapping. Mapping can be shared or private. and it checks for Hugetlb counter (Total, Free, Reserve, Surplus) in /proc/meminfo and compare them with expected (calculated) value. if all checks are successful, the test passes.
--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap10.c | 438 ++++++++++++++++++ 3 files changed, 440 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c
runtest/hugetlb +1 -0
@@ -6,6 +6,7 @@ hugemmap06 hugemmap06 hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 +hugemmap10 hugemmap10 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -m
testcases/kernel/mem/.gitignore +1 -0
@@ -7,6 +7,7 @@ /hugetlb/hugemmap/hugemmap07 /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 +/hugetlb/hugemmap/hugemmap10 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +438 -0
438 lines not on this page · raw message
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Hi!
Quoted 36 lines
runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap10.c | 438 ++++++++++++++++++ 3 files changed, 440 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.cruntest/hugetlb +1
-0@@ -6,6 +6,7 @@ hugemmap06 hugemmap06 hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 +hugemmap10 hugemmap10 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -mtestcases/kernel/mem/.gitignore +1
-0@@ -7,6 +7,7 @@ /hugetlb/hugemmap/hugemmap07 /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 +/hugetlb/hugemmap/hugemmap10 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +0
-0
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 10
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0@@ -0,0 +1,438 @@ +// SPDX-License-Identifier: LGPL-2.1-or-later +/* +* Copyright (C) 2005-2007 IBM Corporation. +* Author: David Gibson & Adam Litke +*/ + +/*\ +* [Description] +* +* Counters:
^
Again this wouldn't render nicely in asciidoc.
Quoted 72 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +72
-0+* This Test perform mmap and unmap and write operation on hugetlb file +* based mapping. Mapping can be shared or private. and it checks for +* Hugetlb counter (Total, Free, Reserve, Surplus) in /proc/meminfo and +* compare them with expected (calculated) value. if all checks are +* successful, the test passes. +* +*/ + +#define _GNU_SOURCE +#include <unistd.h> +#include <stdio.h> +#include <sys/mount.h> +#include <limits.h> +#include <sys/param.h> +#include <sys/types.h> +#include <setjmp.h> + +#include "hugetlb.h" + +#define MNTPOINT "hugetlbfs/" + +static long hpage_size; +static int private_resv; + +#define NR_SLOTS 2 +#define SL_SETUP 0 +#define SL_TEST 1 +static int map_fd[NR_SLOTS ]; +static char *map_addr[NR_SLOTS ]; +static unsigned long map_size[NR_SLOTS ]; +static unsigned int touched[NR_SLOTS ]; + +static long prev_total; +static long prev_free; +static long prev_resv; +static long prev_surp; +static jmp_buf buf; + +static void read_meminfo_huge (long *total,long *free,long *resv,long *surp) +{ + *total =SAFE_READ_MEMINFO (MEMINFO_HPAGE_TOTAL ); + *free =SAFE_READ_MEMINFO (MEMINFO_HPAGE_FREE ); + *resv =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); + *surp =SAFE_READ_MEMINFO (MEMINFO_HPAGE_SURP ); +} + +static int kernel_has_private_reservations (void ) +{ +int fd; +long t, f, r, s; +long nt, nf, nr, ns; +void *map; + +read_meminfo_huge (&t, &f, &r, &s); + fd =tst_creat_unlinked (MNTPOINT ); + + map =SAFE_MMAP (NULL , hpage_size,PROT_READ |PROT_WRITE ,MAP_PRIVATE , fd,0 ); + +read_meminfo_huge (&nt, &nf, &nr, &ns); + +SAFE_MUNMAP (map, hpage_size); +SAFE_CLOSE (fd); + +/* +* There are only three valid cases: +* 1) If a surplus page was allocated to create a reservation, all +* four pool counters increment +* 2) All counters remain the same except for Hugepages_Rsvd, then +* a reservation was created using an existing pool page. +* 3) All counters remain the same, indicates that no reservation has +* been created +*/
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 92
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+if ((nt == t +1 ) && (nf == f +1 ) && (ns == s +1 ) && (nr == r +1 )) +return 1 ; +else if ((nt == t) && (nf == f) && (ns == s)) { +if (nr == r +1 ) +return 1 ; +else if (nr == r) +return 0 ; + }else + tst_brk(TCONF, "bad counter state - " + "T:%li F:%li R:%li S:%li -> T:%li F:%li R:%li S:%li\n",
^ Do not print newline
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 93
Quoted 1 line
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +1
-0+ t, f, r, s, nt, nf, nr, ns);
This is confusing for no good reason. We are doing return in the if () blcoks, so there is no reason to use else at all. This would be much more readable as:
if (...)
reutrn 1;
if (...) {
if (...)
reutrn 1;
else
return 0;
}
tst_brk(TCONF, "...");Quoted 18 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +18
-0+return -1 ; +} + +static void verify_counters (int line,long et,long ef,long er,long es) +{ +long t, f, r, s; +long c, ec; +char *huge_info_name; + +read_meminfo_huge (&t, &f, &r, &s); + +if (t != et) { + c = t; + ec = et; + huge_info_name =MEMINFO_HPAGE_TOTAL ; + }else if (f != ef) { + c = f; + ec = ef;
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 121
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+ huge_info_name =MEMINFO_HPAGE_FREE ; + }else if (r != er) { + c = r; + ec = er; + huge_info_name =MEMINFO_HPAGE_RSVD ; + }else if (s != es) { + c = s; + ec = es; + huge_info_name =MEMINFO_HPAGE_SURP ; + }else {
I think that it would be better to actually print TFAIL for each of the values not just the first that is different.
Something as:
int fail = 0;
if (t != et) {
tst_res(TFAIL, ...);
fail++;
}
if (f != ef) {
...
}
...
if (fail)
return 1;
...testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 129
Quoted 8 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +8
-0+ prev_total = t; + prev_free = f; + prev_resv = r; + prev_surp = s; +return ; + } + + tst_res(TFAIL, "Failure Line %i: Bad %s expected %li, actual %li",
^
Never print "Fail/Pass" with tst_res() it's printed based on the flag passed to it.
The output would contain Fail and Failed at the same time.
Quoted 43 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +43
-0+ line, huge_info_name, ec, c); +longjmp (buf,1 ); +} + +/* Memory operations: +* Each of these has a predefined effect on the counters +*/ +static void set_nr_hugepages_ (long count,int line) +{ +long min_size; +long et, ef, er, es; + +SAFE_FILE_PRINTF (PATH_NR_HPAGES ,"%lu" , count); + +/* The code below is based on set_max_huge_pages in mm/hugetlb.c */ + es = prev_surp; + et = prev_total; + ef = prev_free; + er = prev_resv; + +/* +* Increase the pool size +* First take pages out of surplus state. Then make up the +* remaining difference by allocating fresh huge pages. +*/ +while (es && count > et - es) + es--; +while (count > et - es) { + et++; + ef++; + } +if (count >= et - es) + goto out; + +/* +* Decrease the pool size +* First return free pages to the buddy allocator (being careful +* to keep enough around to satisfy reservations). Then place +* pages into surplus state as needed so the pool will shrink +* to the desired size as pages become free. +*/ + min_size =MAX (count, er + et - ef); +while (min_size < et - es) {
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 182
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+ ef--; + et--; + } +while (count < et - es) + es++; + +out: +verify_counters (line, et, ef, er, es); +} +#define set_nr_hugepages (c) set_nr_hugepages_(c, __LINE__)
I think that instead of the __LINE__ it would make more sense to pass the test description as a string as we do with test_counters()
Quoted 168 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +166
-0+static void map_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; + + map_fd[s] =tst_creat_unlinked (MNTPOINT ); + map_size[s] = hpages * hpage_size; + map_addr[s] =SAFE_MMAP (NULL , map_size[s],PROT_READ |PROT_WRITE , flags, + map_fd[s],0 ); + touched[s] =0 ; + + et = prev_total; + ef = prev_free; + er = prev_resv; + es = prev_surp; +/* +* When using MAP_SHARED, a reservation will be created to guarantee +* pages to the process. If not enough pages are available to +* satisfy the reservation, surplus pages are added to the pool. +* NOTE: This code assumes that the whole mapping needs to be +* reserved and hence, will not work with partial reservations. +* +* If the kernel supports private reservations, then MAP_PRIVATE +* mappings behave like MAP_SHARED at mmap time. Otherwise, +* no counter updates will occur. +*/ +if ((flags &MAP_SHARED ) || private_resv) { +unsigned long shortfall =0 ; + +if (hpages + prev_resv > prev_free) + shortfall = hpages - prev_free + prev_resv; + et += shortfall; + ef += shortfall; + er += hpages; + es += shortfall; + } + +verify_counters (line, et, ef, er, es); +} +#define map (s, h, f) map_(s, h, f, __LINE__) + +static void unmap_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; +unsigned long i; + +SAFE_MUNMAP (map_addr[s], map_size[s]); +SAFE_CLOSE (map_fd[s]); + map_addr[s] =NULL ; + map_size[s] =0 ; + + et = prev_total; + ef = prev_free; + er = prev_resv; + es = prev_surp; + +/* +* When a VMA is unmapped, the instantiated (touched) pages are +* freed. If the pool is in a surplus state, pages are freed to the +* buddy allocator, otherwise they go back into the hugetlb pool. +* NOTE: This code assumes touched pages have only one user. +*/ +for (i =0 ; i < touched[s]; i++) { +if (es) { + et--; + es--; + }else + ef++; + } + +/* +* mmap may have created some surplus pages to accommodate a +* reservation. If those pages were not touched, then they will +* not have been freed by the code above. Free them here. +*/ +if ((flags &MAP_SHARED ) || private_resv) { +int unused_surplus =MIN (hpages - touched[s], es); + + et -= unused_surplus; + ef -= unused_surplus; + er -= hpages - touched[s]; + es -= unused_surplus; + } + +verify_counters (line, et, ef, er, es); +} +#define unmap (s, h, f) unmap_(s, h, f, __LINE__) + +static void touch_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; +int nr; +char *c; + +for (c = map_addr[s], nr = hpages; + hpages && c < map_addr[s] + map_size[s]; + c += hpage_size, nr--) + *c = (char ) (nr %2 ); +/* +* Keep track of how many pages were touched since we can't easily +* detect that from user space. +* NOTE: Calling this function more than once for a mmap may yield +* results you don't expect. Be careful :) +*/ + touched[s] =MAX (touched[s], hpages); + +/* +* Shared (and private when supported) mappings and consume resv pages +* that were previously allocated. Also deduct them from the free count. +* +* Unreserved private mappings may need to allocate surplus pages to +* satisfy the fault. The surplus pages become part of the pool +* which could elevate total, free, and surplus counts. resv is +* unchanged but free must be decreased. +*/ +if (flags &MAP_SHARED || private_resv) { + et = prev_total; + ef = prev_free - hpages; + er = prev_resv - hpages; + es = prev_surp; + }else { +if (hpages + prev_resv > prev_free) + et = prev_total + (hpages - prev_free + prev_resv); +else + et = prev_total; + er = prev_resv; + es = prev_surp + et - prev_total; + ef = prev_free - hpages + et - prev_total; + } +verify_counters (line, et, ef, er, es); +} +#define touch (s, h, f) touch_(s, h, f, __LINE__) +static void test_counters (char *desc,int base_nr) +{ +tst_res (TINFO ,"%s..." , desc); +set_nr_hugepages (base_nr); + +/* untouched, shared mmap */ +map (SL_TEST ,1 ,MAP_SHARED ); +unmap (SL_TEST ,1 ,MAP_SHARED ); + +/* untouched, private mmap */ +map (SL_TEST ,1 ,MAP_PRIVATE ); +unmap (SL_TEST ,1 ,MAP_PRIVATE ); + +/* touched, shared mmap */ +map (SL_TEST ,1 ,MAP_SHARED ); +touch (SL_TEST ,1 ,MAP_SHARED ); +unmap (SL_TEST ,1 ,MAP_SHARED ); + +/* touched, private mmap */ +map (SL_TEST ,1 ,MAP_PRIVATE ); +touch (SL_TEST ,1 ,MAP_PRIVATE ); +unmap (SL_TEST ,1 ,MAP_PRIVATE ); + +/* Explicit resizing during outstanding surplus */ +/* Consume surplus when growing pool */ +map (SL_TEST ,2 ,MAP_SHARED ); +set_nr_hugepages (MAX (base_nr,1 )); + +/* Add pages once surplus is consumed */ +set_nr_hugepages (MAX (base_nr,3 )); + +/* Release free huge pages first */ +set_nr_hugepages (MAX (base_nr,2 )); + +/* When shrinking beyond committed level, increase surplus */
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 360
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+set_nr_hugepages (base_nr); + +/* Upon releasing the reservation, reduce surplus counts */ +unmap (SL_TEST ,2 ,MAP_SHARED ); +tst_res (TINFO ,"OK" ); +} + +static void per_iteration_cleanup (void ) +{ +int nr =0 ;
This is confusing for no good reason, the nr should better be initialized in the for loop instead as it's usually done.
Quoted 6 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +6
-0+ prev_total =0 ; + prev_free =0 ; + prev_resv =0 ; + prev_surp =0 ; +for (; nr <NR_SLOTS ; nr++) { +if (map_fd[nr] >0 )
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 377
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+SAFE_CLOSE (map_fd[nr]); + } +} + +static void run_test (void ) +{ +int base_nr =0 ; + +SAFE_FILE_PRINTF (PATH_OC_HPAGES ,"%lu" , tst_hugepages); + private_resv =kernel_has_private_reservations ();
This should be done once in the test setup().
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 380
Quoted 2 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +2
-0+if (setjmp (buf)) + goto cleanup;
This is way beyond ugly. I guess that it would be cleaner to actually return a pass/fail from the test_counters() function and break the for() loop based on that value instead of this longjmp trickery.
Also I do not think that the current code is correct anyway, because we skip the unmap() call. So I suppose the correct way would be:
res = test_counters("Untouched, shared", base_nr);
unmap(SL_SETUP, 1, MAP_SHARED);
if (res)
break;Or eventually we can make the desing better by unmaping any leftover mappings in the per_iteration_cleanup(). Then we can just do:
map() if (test_coutners(...) break; unmap()
Quoted 60 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +57
-0+for (base_nr =0 ; base_nr <=3 ; base_nr++) { +tst_res (TINFO ,"Base pool size: %i" , base_nr); +/* Run the tests with a clean slate */ +test_counters ("Clean" , base_nr); + +/* Now with a pre-existing untouched, shared mmap */ +map (SL_SETUP ,1 ,MAP_SHARED ); +test_counters ("Untouched, shared" , base_nr); +unmap (SL_SETUP ,1 ,MAP_SHARED ); + +/* Now with a pre-existing untouched, private mmap */ +map (SL_SETUP ,1 ,MAP_PRIVATE ); +test_counters ("Untouched, private" , base_nr); +unmap (SL_SETUP ,1 ,MAP_PRIVATE ); + +/* Now with a pre-existing touched, shared mmap */ +map (SL_SETUP ,1 ,MAP_SHARED ); +touch (SL_SETUP ,1 ,MAP_SHARED ); +test_counters ("Touched, shared" , base_nr); +unmap (SL_SETUP ,1 ,MAP_SHARED ); + +/* Now with a pre-existing touched, private mmap */ +map (SL_SETUP ,1 ,MAP_PRIVATE ); +touch (SL_SETUP ,1 ,MAP_PRIVATE ); +test_counters ("Touched, private" , base_nr); +unmap (SL_SETUP ,1 ,MAP_PRIVATE ); + } +tst_res (TPASS ,"Hugepages Counters works as expected." ); +cleanup: +per_iteration_cleanup (); +} + +static void setup (void ) +{ + hpage_size =SAFE_READ_MEMINFO (MEMINFO_HPAGE_SIZE )*1024 ; +} + +static void cleanup (void ) +{ +per_iteration_cleanup (); +} + +static struct tst_test test = { + .needs_root =1 , + .mntpoint =MNTPOINT , + .needs_hugetlbfs =1 , + .save_restore = (const struct tst_path_val []) { + {PATH_OC_HPAGES ,NULL }, + {PATH_NR_HPAGES ,NULL }, + {} + }, + .setup = setup, + .cleanup = cleanup, + .test_all = run_test, + .hugepages = {3 ,TST_NEEDS }, +}; +Signature · 1 line
2.31.1
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Hi,
Thanks for reviewing the patch.
Quoted 48 lines · Cyril Hrubis
Hi!
Quoted 36 lines
runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap10.c | 438 ++++++++++++++++++ 3 files changed, 440 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.cruntest/hugetlb +1
-0@@ -6,6 +6,7 @@ hugemmap06 hugemmap06 hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 +hugemmap10 hugemmap10 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -mtestcases/kernel/mem/.gitignore +1
-0@@ -7,6 +7,7 @@ /hugetlb/hugemmap/hugemmap07 /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 +/hugetlb/hugemmap/hugemmap10 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +0
-0testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 10
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0@@ -0,0 +1,438 @@ +// SPDX-License-Identifier: LGPL-2.1-or-later +/* +* Copyright (C) 2005-2007 IBM Corporation. +* Author: David Gibson & Adam Litke +*/ + +/*\ +* [Description] +* +* Counters: ^
Quoted 2 lines
Again this wouldn't render nicely in asciidoc.
OOps, Missed it, Will updated it.
Quoted 94 lines
Quoted 72 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +72
-0+* This Test perform mmap and unmap and write operation on hugetlb file +* based mapping. Mapping can be shared or private. and it checks for +* Hugetlb counter (Total, Free, Reserve, Surplus) in /proc/meminfo and +* compare them with expected (calculated) value. if all checks are +* successful, the test passes. +* +*/ + +#define _GNU_SOURCE +#include <unistd.h> +#include <stdio.h> +#include <sys/mount.h> +#include <limits.h> +#include <sys/param.h> +#include <sys/types.h> +#include <setjmp.h> + +#include "hugetlb.h" + +#define MNTPOINT "hugetlbfs/" + +static long hpage_size; +static int private_resv; + +#define NR_SLOTS 2 +#define SL_SETUP 0 +#define SL_TEST 1 +static int map_fd[NR_SLOTS ]; +static char *map_addr[NR_SLOTS ]; +static unsigned long map_size[NR_SLOTS ]; +static unsigned int touched[NR_SLOTS ]; + +static long prev_total; +static long prev_free; +static long prev_resv; +static long prev_surp; +static jmp_buf buf; + +static void read_meminfo_huge (long *total,long *free,long *resv,long *surp) +{ + *total =SAFE_READ_MEMINFO (MEMINFO_HPAGE_TOTAL ); + *free =SAFE_READ_MEMINFO (MEMINFO_HPAGE_FREE ); + *resv =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); + *surp =SAFE_READ_MEMINFO (MEMINFO_HPAGE_SURP ); +} + +static int kernel_has_private_reservations (void ) +{ +int fd; +long t, f, r, s; +long nt, nf, nr, ns; +void *map; + +read_meminfo_huge (&t, &f, &r, &s); + fd =tst_creat_unlinked (MNTPOINT ); + + map =SAFE_MMAP (NULL , hpage_size,PROT_READ |PROT_WRITE ,MAP_PRIVATE , fd,0 ); + +read_meminfo_huge (&nt, &nf, &nr, &ns); + +SAFE_MUNMAP (map, hpage_size); +SAFE_CLOSE (fd); + +/* +* There are only three valid cases: +* 1) If a surplus page was allocated to create a reservation, all +* four pool counters increment +* 2) All counters remain the same except for Hugepages_Rsvd, then +* a reservation was created using an existing pool page. +* 3) All counters remain the same, indicates that no reservation has +* been created +*/ testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 92
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+if ((nt == t +1 ) && (nf == f +1 ) && (ns == s +1 ) && (nr == r +1 )) +return 1 ; +else if ((nt == t) && (nf == f) && (ns == s)) { +if (nr == r +1 ) +return 1 ; +else if (nr == r) +return 0 ; + }else + tst_brk(TCONF, "bad counter state - " + "T:%li F:%li R:%li S:%li -> T:%li F:%li R:%li S:%li\n",^ Do not print newlinetestcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 93
Quoted 1 line
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +1
-0+ t, f, r, s, nt, nf, nr, ns);This is confusing for no good reason. We are doing return in the if () blcoks, so there is no reason to use else at all. This would be much more readable as:
Quoted 14 lines
if (...)
reutrn 1;
if (...) {
if (...)
reutrn 1;
else
return 0;
}
tst_brk(TCONF, "...");Yeah. Will update it.
Quoted 45 lines
Quoted 18 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +18
-0+return -1 ; +} + +static void verify_counters (int line,long et,long ef,long er,long es) +{ +long t, f, r, s; +long c, ec; +char *huge_info_name; + +read_meminfo_huge (&t, &f, &r, &s); + +if (t != et) { + c = t; + ec = et; + huge_info_name =MEMINFO_HPAGE_TOTAL ; + }else if (f != ef) { + c = f; + ec = ef;testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 121
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+ huge_info_name =MEMINFO_HPAGE_FREE ; + }else if (r != er) { + c = r; + ec = er; + huge_info_name =MEMINFO_HPAGE_RSVD ; + }else if (s != es) { + c = s; + ec = es; + huge_info_name =MEMINFO_HPAGE_SURP ; + }else {I think that it would be better to actually print TFAIL for each of the values not just the first that is different.
Something as:
int fail = 0; if (t != et) { tst_res(TFAIL, ...); fail++; } if (f != ef) { ... }
Quoted 8 lines
... if (fail) return 1; ...
Yeah. That way user will have more information. Will update it.
Quoted 12 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 129
Quoted 8 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +8
-0+ prev_total = t; + prev_free = f; + prev_resv = r; + prev_surp = s; +return ; + } + + tst_res(TFAIL, "Failure Line %i: Bad %s expected %li, actual %li",^
Never print "Fail/Pass" withtst_res()it's printed based on the flag passed to it.
Quoted 2 lines
The output would contain Fail and Failed at the same time.
This doesn't say failed.
It says failure-line from which the failure originated.
like,
hugemmap10.c:63: FAIL: Failure Line 321, Bad HugePages_Free: expected 5, actual 4
Quoted 48 lines
Quoted 48 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +48
-0+ line, huge_info_name, ec, c); +longjmp (buf,1 ); +} + +/* Memory operations: +* Each of these has a predefined effect on the counters +*/ +static void set_nr_hugepages_ (long count,int line) +{ +long min_size; +long et, ef, er, es; + +SAFE_FILE_PRINTF (PATH_NR_HPAGES ,"%lu" , count); + +/* The code below is based on set_max_huge_pages in mm/hugetlb.c */ + es = prev_surp; + et = prev_total; + ef = prev_free; + er = prev_resv; + +/* +* Increase the pool size +* First take pages out of surplus state. Then make up the +* remaining difference by allocating fresh huge pages. +*/ +while (es && count > et - es) + es--; +while (count > et - es) { + et++; + ef++; + } +if (count >= et - es) + goto out; + +/* +* Decrease the pool size +* First return free pages to the buddy allocator (being careful +* to keep enough around to satisfy reservations). Then place +* pages into surplus state as needed so the pool will shrink +* to the desired size as pages become free. +*/ + min_size =MAX (count, er + et - ef); +while (min_size < et - es) { + ef--; + et--; + } +while (count < et - es) + es++;
Quoted 9 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 182
Quoted 5 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +5
-0+ +out: +verify_counters (line, et, ef, er, es); +} +#define set_nr_hugepages (c) set_nr_hugepages_(c, __LINE__)I think that instead of the
__LINE__it would make more sense to pass the test description as a string as we do withtest_counters()
That will require each line inside test_counters to have unique string description for map, touch, unmap, set_nr_hugepages calls, similiary inside for loop. Which will make user hard to find where they have to look for origin of issue, unless they search for string match.
like,
/* untouched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private no touch"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory mmaped private no touched"); /* touched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private followed by touch"); touch(SL_TEST, 1, MAP_PRIVATE, "touch memory mmaped private"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory touched mmaped private");
But I agree, a unique description, will give more information on test run logs.
What do you think?
Quoted 173 lines
Quoted 173 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +171
-0+static void map_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; + + map_fd[s] =tst_creat_unlinked (MNTPOINT ); + map_size[s] = hpages * hpage_size; + map_addr[s] =SAFE_MMAP (NULL , map_size[s],PROT_READ |PROT_WRITE , flags, + map_fd[s],0 ); + touched[s] =0 ; + + et = prev_total; + ef = prev_free; + er = prev_resv; + es = prev_surp; +/* +* When using MAP_SHARED, a reservation will be created to guarantee +* pages to the process. If not enough pages are available to +* satisfy the reservation, surplus pages are added to the pool. +* NOTE: This code assumes that the whole mapping needs to be +* reserved and hence, will not work with partial reservations. +* +* If the kernel supports private reservations, then MAP_PRIVATE +* mappings behave like MAP_SHARED at mmap time. Otherwise, +* no counter updates will occur. +*/ +if ((flags &MAP_SHARED ) || private_resv) { +unsigned long shortfall =0 ; + +if (hpages + prev_resv > prev_free) + shortfall = hpages - prev_free + prev_resv; + et += shortfall; + ef += shortfall; + er += hpages; + es += shortfall; + } + +verify_counters (line, et, ef, er, es); +} +#define map (s, h, f) map_(s, h, f, __LINE__) + +static void unmap_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; +unsigned long i; + +SAFE_MUNMAP (map_addr[s], map_size[s]); +SAFE_CLOSE (map_fd[s]); + map_addr[s] =NULL ; + map_size[s] =0 ; + + et = prev_total; + ef = prev_free; + er = prev_resv; + es = prev_surp; + +/* +* When a VMA is unmapped, the instantiated (touched) pages are +* freed. If the pool is in a surplus state, pages are freed to the +* buddy allocator, otherwise they go back into the hugetlb pool. +* NOTE: This code assumes touched pages have only one user. +*/ +for (i =0 ; i < touched[s]; i++) { +if (es) { + et--; + es--; + }else + ef++; + } + +/* +* mmap may have created some surplus pages to accommodate a +* reservation. If those pages were not touched, then they will +* not have been freed by the code above. Free them here. +*/ +if ((flags &MAP_SHARED ) || private_resv) { +int unused_surplus =MIN (hpages - touched[s], es); + + et -= unused_surplus; + ef -= unused_surplus; + er -= hpages - touched[s]; + es -= unused_surplus; + } + +verify_counters (line, et, ef, er, es); +} +#define unmap (s, h, f) unmap_(s, h, f, __LINE__) + +static void touch_ (int s,int hpages,int flags,int line) +{ +long et, ef, er, es; +int nr; +char *c; + +for (c = map_addr[s], nr = hpages; + hpages && c < map_addr[s] + map_size[s]; + c += hpage_size, nr--) + *c = (char ) (nr %2 ); +/* +* Keep track of how many pages were touched since we can't easily +* detect that from user space. +* NOTE: Calling this function more than once for a mmap may yield +* results you don't expect. Be careful :) +*/ + touched[s] =MAX (touched[s], hpages); + +/* +* Shared (and private when supported) mappings and consume resv pages +* that were previously allocated. Also deduct them from the free count. +* +* Unreserved private mappings may need to allocate surplus pages to +* satisfy the fault. The surplus pages become part of the pool +* which could elevate total, free, and surplus counts. resv is +* unchanged but free must be decreased. +*/ +if (flags &MAP_SHARED || private_resv) { + et = prev_total; + ef = prev_free - hpages; + er = prev_resv - hpages; + es = prev_surp; + }else { +if (hpages + prev_resv > prev_free) + et = prev_total + (hpages - prev_free + prev_resv); +else + et = prev_total; + er = prev_resv; + es = prev_surp + et - prev_total; + ef = prev_free - hpages + et - prev_total; + } +verify_counters (line, et, ef, er, es); +} +#define touch (s, h, f) touch_(s, h, f, __LINE__) +static void test_counters (char *desc,int base_nr) +{ +tst_res (TINFO ,"%s..." , desc); +set_nr_hugepages (base_nr); + +/* untouched, shared mmap */ +map (SL_TEST ,1 ,MAP_SHARED ); +unmap (SL_TEST ,1 ,MAP_SHARED ); + +/* untouched, private mmap */ +map (SL_TEST ,1 ,MAP_PRIVATE ); +unmap (SL_TEST ,1 ,MAP_PRIVATE ); + +/* touched, shared mmap */ +map (SL_TEST ,1 ,MAP_SHARED ); +touch (SL_TEST ,1 ,MAP_SHARED ); +unmap (SL_TEST ,1 ,MAP_SHARED ); + +/* touched, private mmap */ +map (SL_TEST ,1 ,MAP_PRIVATE ); +touch (SL_TEST ,1 ,MAP_PRIVATE ); +unmap (SL_TEST ,1 ,MAP_PRIVATE ); + +/* Explicit resizing during outstanding surplus */ +/* Consume surplus when growing pool */ +map (SL_TEST ,2 ,MAP_SHARED ); +set_nr_hugepages (MAX (base_nr,1 )); + +/* Add pages once surplus is consumed */ +set_nr_hugepages (MAX (base_nr,3 )); + +/* Release free huge pages first */ +set_nr_hugepages (MAX (base_nr,2 )); + +/* When shrinking beyond committed level, increase surplus */ +set_nr_hugepages (base_nr); + +/* Upon releasing the reservation, reduce surplus counts */ +unmap (SL_TEST ,2 ,MAP_SHARED ); +tst_res (TINFO ,"OK" );
Quoted 9 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 360
Quoted 5 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +5
-0+} + +static void per_iteration_cleanup (void ) +{ +int nr =0 ;This is confusing for no good reason, the nr should better be initialized in the for loop instead as it's usually done.
Ok, Will update it.
Quoted 10 lines
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +10
-0+ prev_total =0 ; + prev_free =0 ; + prev_resv =0 ; + prev_surp =0 ; +for (; nr <NR_SLOTS ; nr++) { +if (map_fd[nr] >0 ) +SAFE_CLOSE (map_fd[nr]); + } +} +
Quoted 9 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 377
Quoted 6 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +6
-0+static void run_test (void ) +{ +int base_nr =0 ; + +SAFE_FILE_PRINTF (PATH_OC_HPAGES ,"%lu" , tst_hugepages); + private_resv =kernel_has_private_reservations ();This should be done once in the test
setup().
Yeah, Will move it.
Quoted 11 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 380
Quoted 2 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +2
-0+if (setjmp (buf)) + goto cleanup;This is way beyond ugly. I guess that it would be cleaner to actually return a pass/fail from the
test_counters()function and break thefor()loop based on that value instead of this longjmp trickery.Also I do not think that the current code is correct anyway, because we skip the
unmap()call. So I suppose the correct way would be:
Quoted 6 lines
res = test_counters("Untouched, shared", base_nr);
unmap(SL_SETUP, 1, MAP_SHARED);
if (res)
break;I was thinking same first. But Thought of adding the checks at each line in test_counters(...) and inside for loop, will make the code unclean. Hence, I chose the setjmp/longjmp mechanism. Only drawback is that mapping was not getting cleaned up (unmap), That we can add in per_iteration_cleanup.
What do you think?
Quoted 8 lines
Or eventually we can make the desing better by unmaping any leftover mappings in the
per_iteration_cleanup(). Then we can just do:map() if (test_coutners(...) break; unmap()
map and unmap do also require return checks, as they also perform verify_counter on expected and original counters.
yeah, I will add unmap in per_iteration_cleanup.
Quoted 67 lines
Quoted 60 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +57
-0+for (base_nr =0 ; base_nr <=3 ; base_nr++) { +tst_res (TINFO ,"Base pool size: %i" , base_nr); +/* Run the tests with a clean slate */ +test_counters ("Clean" , base_nr); + +/* Now with a pre-existing untouched, shared mmap */ +map (SL_SETUP ,1 ,MAP_SHARED ); +test_counters ("Untouched, shared" , base_nr); +unmap (SL_SETUP ,1 ,MAP_SHARED ); + +/* Now with a pre-existing untouched, private mmap */ +map (SL_SETUP ,1 ,MAP_PRIVATE ); +test_counters ("Untouched, private" , base_nr); +unmap (SL_SETUP ,1 ,MAP_PRIVATE ); + +/* Now with a pre-existing touched, shared mmap */ +map (SL_SETUP ,1 ,MAP_SHARED ); +touch (SL_SETUP ,1 ,MAP_SHARED ); +test_counters ("Touched, shared" , base_nr); +unmap (SL_SETUP ,1 ,MAP_SHARED ); + +/* Now with a pre-existing touched, private mmap */ +map (SL_SETUP ,1 ,MAP_PRIVATE ); +touch (SL_SETUP ,1 ,MAP_PRIVATE ); +test_counters ("Touched, private" , base_nr); +unmap (SL_SETUP ,1 ,MAP_PRIVATE ); + } +tst_res (TPASS ,"Hugepages Counters works as expected." ); +cleanup: +per_iteration_cleanup (); +} + +static void setup (void ) +{ + hpage_size =SAFE_READ_MEMINFO (MEMINFO_HPAGE_SIZE )*1024 ; +} + +static void cleanup (void ) +{ +per_iteration_cleanup (); +} + +static struct tst_test test = { + .needs_root =1 , + .mntpoint =MNTPOINT , + .needs_hugetlbfs =1 , + .save_restore = (const struct tst_path_val []) { + {PATH_OC_HPAGES ,NULL }, + {PATH_NR_HPAGES ,NULL }, + {} + }, + .setup = setup, + .cleanup = cleanup, + .test_all = run_test, + .hugepages = {3 ,TST_NEEDS }, +}; +Signature · 1 line
2.31.1Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Hi!
Quoted 12 lines
Quoted 12 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 129
Quoted 8 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +8
-0+ prev_total = t; + prev_free = f; + prev_resv = r; + prev_surp = s; +return ; + } + + tst_res(TFAIL, "Failure Line %i: Bad %s expected %li, actual %li",^
Never print "Fail/Pass" withtst_res()it's printed based on the flag passed to it.
Quoted 6 lines
Quoted 2 lines
The output would contain Fail and Failed at the same time.
This doesn't say failed.
It says failure-line from which the failure originated.
like,
hugemmap10.c:63: FAIL: Failure Line 321, BadHugePages_Free: expected 5, actual 4
However that is still redundant information, right?
The meaning of "FAIL: line xyz" and "FAIL: failure line xyz" is the same, the second one is just longer. Let's keep the messages short and to the point.
Quoted 20 lines
Quoted 3 lines
I think that instead of the
__LINE__it would make more sense to pass the test description as a string as we do withtest_counters()That will require each line inside
test_countersto have unique string description for map, touch, unmap,set_nr_hugepagescalls, similiary inside for loop. Which will make user hard to find where they have to look for origin of issue, unless they search for string match.like,
/* untouched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private no touch"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory mmaped private no touched"); /* touched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private followed by touch"); touch(SL_TEST, 1, MAP_PRIVATE, "touch memory mmaped private"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory touched mmaped private");
Quoted 4 lines
But I agree, a unique description, will give more information on test run logs.
What do you think?
Sounds good.
Quoted 18 lines
Quoted 11 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 380
Quoted 2 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +2
-0+if (setjmp (buf)) + goto cleanup;This is way beyond ugly. I guess that it would be cleaner to actually return a pass/fail from the
test_counters()function and break thefor()loop based on that value instead of this longjmp trickery.Also I do not think that the current code is correct anyway, because we skip the
unmap()call. So I suppose the correct way would be:Quoted 6 lines
res = test_counters("Untouched, shared", base_nr); unmap(SL_SETUP, 1, MAP_SHARED); if (res) break;
Quoted 6 lines
I was thinking same first. But Thought of adding the checks at each line in
test_counters(...)and inside for loop, will make the code unclean. Hence, I chose the setjmp/longjmp mechanism. Only drawback is that mapping was not getting cleaned up (unmap), That we can add inper_iteration_cleanup.What do you think?
The reason why I do not like the longjmp() is that it obscures the code flow. If we have explicit if () and break; it's clear what is happening. With setjmp() you have to search the code for corresponding longjmp() calls. It's not that bad in this case but I would still stick to avoiding longjmp() unless really necessary.
Quoted 10 lines
Quoted 8 lines
Or eventually we can make the desing better by unmaping any leftover mappings in the
per_iteration_cleanup(). Then we can just do:map() if (test_coutners(...) break; unmap()map and unmap do also require return checks, as they also perform
verify_counteron expected and original counters.
I guess that we can also put the map() (touch()) test_counters() unamp() sequence to a do_test() fuction then call it from the for() loop in run_test(). That would make the code a bit cleaner.
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Quoted 15 lines · Cyril Hrubis
Hi!
Quoted 14 lines
Quoted 14 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 129
Quoted 8 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +8
-0+ prev_total = t; + prev_free = f; + prev_resv = r; + prev_surp = s; +return ; + } + + tst_res(TFAIL, "Failure Line %i: Bad %s expected %li, actual %li",^
Never print "Fail/Pass" withtst_res()it's printed based on the flag passed to it.The output would contain Fail and Failed at the same time.
Ok Will update it.
Quoted 31 lines
Quoted 4 lines
This doesn't say failed.
It says failure-line from which the failure originated.
like,
hugemmap10.c:63: FAIL: Failure Line 321, BadHugePages_Free: expected 5, actual 4However that is still redundant information, right?
The meaning of "FAIL: line xyz" and "FAIL: failure line xyz" is the same, the second one is just longer. Let's keep the messages short and to the point.
Quoted 20 lines
Quoted 3 lines
I think that instead of the
__LINE__it would make more sense to pass the test description as a string as we do withtest_counters()That will require each line inside
test_countersto have unique string description for map, touch, unmap,set_nr_hugepagescalls, similiary inside for loop. Which will make user hard to find where they have to look for origin of issue, unless they search for string match.like,
/* untouched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private no touch"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory mmaped private no touched"); /* touched, private mmap */ map(SL_TEST, 1, MAP_PRIVATE, "mmap private followed by touch"); touch(SL_TEST, 1, MAP_PRIVATE, "touch memory mmaped private"); unmap(SL_TEST, 1, MAP_PRIVATE, "unmap memory touched mmaped private");
Quoted 7 lines
Quoted 4 lines
But I agree, a unique description, will give more information on test run logs.
What do you think?
Sounds good.
Ok, Will update it with custom msgs.
Quoted 39 lines
Quoted 18 lines
Quoted 11 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c line 380
Quoted 2 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap10.c new file +2
-0+if (setjmp (buf)) + goto cleanup;This is way beyond ugly. I guess that it would be cleaner to actually return a pass/fail from the
test_counters()function and break thefor()loop based on that value instead of this longjmp trickery.Also I do not think that the current code is correct anyway, because we skip the
unmap()call. So I suppose the correct way would be:Quoted 6 lines
res = test_counters("Untouched, shared", base_nr); unmap(SL_SETUP, 1, MAP_SHARED); if (res) break;Quoted 6 lines
I was thinking same first. But Thought of adding the checks at each line in
test_counters(...)and inside for loop, will make the code unclean. Hence, I chose the setjmp/longjmp mechanism. Only drawback is that mapping was not getting cleaned up (unmap), That we can add inper_iteration_cleanup.What do you think?
The reason why I do not like the
longjmp()is that it obscures the code flow. If we have explicit if () and break; it's clear what is happening. Withsetjmp()you have to search the code for correspondinglongjmp()calls. It's not that bad in this case but I would still stick to avoidinglongjmp()unless really necessary.Quoted 8 lines
Quoted 8 lines
Or eventually we can make the desing better by unmaping any leftover mappings in the
per_iteration_cleanup(). Then we can just do:map() if (test_coutners(...) break; unmap()
Quoted 7 lines
Quoted 2 lines
map and unmap do also require return checks, as they also perform
verify_counteron expected and original counters.I guess that we can also put the
map()(touch())test_counters()unamp()sequence to ado_test()fuction then call it from thefor()loop inrun_test(). That would make the code a bit cleaner.
Instead, I am thinking of a defining a macro like this,
#define CHECK_(fun) ({ \
if (fun) { \
break; \
} \
})inside test_counters:
do {
CHECK_(map(...));
CHECK_(touch(...));
CHECK_(unmap(...));
} while(0)inside for loop of run_test:
CHECK_(map(...));
CHECK_(test_counters(...));
CHECK_(unmap(...));
Quoted 6 lines
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Quoted 20 lines · Tarun Sahu
Quoted 4 lines
I guess that we can also put the
map()(touch())test_counters()unamp()sequence to ado_test()fuction then call it from thefor()loop inrun_test(). That would make the code a bit cleaner.Instead, I am thinking of a defining a macro like this,
#define CHECK_(fun) ({ \ if (fun) { \ break; \ } \ })inside
test_counters:do { CHECK_(map(...)); CHECK_(touch(...)); CHECK_(unmap(...)); } while(0)
Quoted 6 lines
inside for loop of
run_test:CHECK_(map(...));
CHECK_(test_counters(...));
CHECK_(unmap(...));
Code will be as clean as the previous, if we can just add CHECK_ in map, unmap, touch macro definition. like..
#define map(a,b,c,d) CHECK_(map_(a, b, c, d))
Quoted 9 lines
Quoted 6 lines
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltpSignature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
In reply to Tarun SahuHi!
Quoted 20 lines
Quoted 4 lines
I guess that we can also put the
map()(touch())test_counters()unamp()sequence to ado_test()fuction then call it from thefor()loop inrun_test(). That would make the code a bit cleaner.Instead, I am thinking of a defining a macro like this,
#define CHECK_(fun) ({ \ if (fun) { \ break; \ } \ })inside
test_counters:do { CHECK_(map(...)); CHECK_(touch(...)); CHECK_(unmap(...)); } while(0)
Quoted 5 lines
inside for loop of
run_test:CHECK_(map(...));
CHECK_(test_counters(...));
CHECK_(unmap(...));
While this is much better than longjmp() it still obscures the codeflow a little bit.
Also I do not think that we need all the braces in the CHECK() macro, it should be enough just to do:
#define CHECK(fun) \ if (fun) \ break;
or even:
#define CHECK(fun) if (fun) break;
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 1/5] Hugetlb: Migrating libhugetlbfs counters
Quoted 37 lines · Cyril Hrubis
Hi!
Quoted 22 lines
Quoted 6 lines
I guess that we can also put the
map()(touch())test_counters()unamp()
sequence to ado_test()fuction then call it from thefor()loop inrun_test(). That would make the code a bit cleaner.Instead, I am thinking of a defining a macro like this,
#define CHECK_(fun) ({ \ if (fun) { \ break; \ } \ })inside
test_counters:do { CHECK_(map(...)); CHECK_(touch(...)); CHECK_(unmap(...)); } while(0)Quoted 5 lines
inside for loop of
run_test:CHECK_(map(...));
CHECK_(test_counters(...));
CHECK_(unmap(...));While this is much better than
longjmp()it still obscures the codeflow
a little bit.Also I do not think that we need all the braces in the
CHECK()macro, it
should be enough just to do:
Quoted 7 lines
#define CHECK(fun) \ if (fun) \ break;or even:
#define CHECK(fun) if (fun) break;
This throws make check warning, It asks to put it in do..while which is not preferable as we want break the parent loop, not the loop added by macro. So I added those brackets.
Quoted 1 line
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
PATCH v2 2/5 Hugetlb: Migrating libhugetlbfs directio
In reply to Tarun SahuMigrating the libhugetlbfs/testcases/direct.c test
Test Description: This Test perform Direct Write/Read from/To hugetlbfs file which is mapped to process address space. The test is checking if it succeeds and data written or read is not corrupted.
--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap11.c | 87 +++++++++++++++++++ 3 files changed, 89 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c
runtest/hugetlb +1 -0
@@ -7,6 +7,7 @@ hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 hugemmap10 hugemmap10 +hugemmap11 hugemmap11 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -m
testcases/kernel/mem/.gitignore +1 -0
@@ -8,6 +8,7 @@ /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 /hugetlb/hugemmap/hugemmap10 +/hugetlb/hugemmap/hugemmap11 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03
testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c new file +87 -0
87 lines not on this page · raw message
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 2/5] Hugetlb: Migrating libhugetlbfs directio
Quoted 93 lines
Migrating the
libhugetlbfs/testcases/direct.ctestTest Description: This Test perform Direct Write/Read from/To hugetlbfs file which is mapped to process address space. The test is checking if it succeeds and data written or read is not corrupted.
Signed-off-by Tarun Sahu <[email protected]>--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap11.c | 87 +++++++++++++++++++ 3 files changed, 89 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.cruntest/hugetlb +1
-0@@ -7,6 +7,7 @@ hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 hugemmap10 hugemmap10 +hugemmap11 hugemmap11 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -mtestcases/kernel/mem/.gitignore +1
-0@@ -8,6 +8,7 @@ /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 /hugetlb/hugemmap/hugemmap10 +/hugetlb/hugemmap/hugemmap11 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c new file +49
-0@@ -0,0 +1,87 @@ +// SPDX-License-Identifier: LGPL-2.1-or-later +/* +* Copyright (C) 2005-2006 IBM Corporation. +* Author: David Gibson & Adam Litke +*/ + +/*\ +* [Description] +* +* This Test perform Direct Write/Read from/To hugetlbfs file +* which is mapped to process address space. The test is checking if it +* succeeds and data written or read is not corrupted. +* +*/ + +#define _GNU_SOURCE +#include <stdio.h> +#include <sys/mount.h> +#include <limits.h> +#include <sys/param.h> +#include <sys/types.h> + +#include "hugetlb.h" + +#define P0 "ffffffff" +#define IOSZ 4096 +#define NORMAL_PATH "" +#define MNTPOINT "hugetlbfs/" + +static long hpage_size; +static int fd =-1 , nfd =-1 ; + +static void run_test (void ) +{ +void *p; + char buf[IOSZ] __attribute__((aligned(IOSZ))); + + fd =tst_creat_unlinked (MNTPOINT ); + nfd =tst_creat_unlinked (NORMAL_PATH ); + p =SAFE_MMAP (NULL , hpage_size,PROT_READ |PROT_WRITE ,MAP_PRIVATE , fd,0 ); +memcpy (p,P0 ,8 ); + +SAFE_WRITE (1 , nfd, p,IOSZ ); +SAFE_LSEEK (nfd,0 ,SEEK_SET ); + +SAFE_READ (1 , nfd, buf,IOSZ ); +if (memcmp (P0 , buf,8 )) { +tst_res (TFAIL ,"Memory mismatch after Direct-IO write" ); + goto cleanup;
testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c line 59
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c new file +10
-0+ } +SAFE_LSEEK (nfd,0 ,SEEK_SET ); + +memset (p,0 ,IOSZ ); +SAFE_READ (1 , nfd, p,IOSZ ); + +if (memcmp (p,P0 ,8 )) +tst_res (TFAIL ,"Memory mismatch after Direct-IO read" ); +else +tst_res (TPASS ,"Successful" );
^
We shoudl write something more meaningful. Something as:
"All data were read and written correctly"
Other than this the rest looks good.
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 2/5] Hugetlb: Migrating libhugetlbfs directio
Hi,
Thanks for reviewring it.
Quoted 107 lines · Cyril Hrubis
Quoted 93 lines
Migrating the
libhugetlbfs/testcases/direct.ctestTest Description: This Test perform Direct Write/Read from/To hugetlbfs file which is mapped to process address space. The test is checking if it succeeds and data written or read is not corrupted.
Signed-off-by Tarun Sahu <[email protected]>--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap11.c | 87 +++++++++++++++++++ 3 files changed, 89 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.cruntest/hugetlb +1
-0@@ -7,6 +7,7 @@ hugemmap07 hugemmap07 hugemmap08 hugemmap08 hugemmap09 hugemmap09 hugemmap10 hugemmap10 +hugemmap11 hugemmap11 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -mtestcases/kernel/mem/.gitignore +1
-0@@ -8,6 +8,7 @@ /hugetlb/hugemmap/hugemmap08 /hugetlb/hugemmap/hugemmap09 /hugetlb/hugemmap/hugemmap10 +/hugetlb/hugemmap/hugemmap11 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c new file +49
-0@@ -0,0 +1,87 @@ +// SPDX-License-Identifier: LGPL-2.1-or-later +/* +* Copyright (C) 2005-2006 IBM Corporation. +* Author: David Gibson & Adam Litke +*/ + +/*\ +* [Description] +* +* This Test perform Direct Write/Read from/To hugetlbfs file +* which is mapped to process address space. The test is checking if it +* succeeds and data written or read is not corrupted. +* +*/ + +#define _GNU_SOURCE +#include <stdio.h> +#include <sys/mount.h> +#include <limits.h> +#include <sys/param.h> +#include <sys/types.h> + +#include "hugetlb.h" + +#define P0 "ffffffff" +#define IOSZ 4096 +#define NORMAL_PATH "" +#define MNTPOINT "hugetlbfs/" + +static long hpage_size; +static int fd =-1 , nfd =-1 ; + +static void run_test (void ) +{ +void *p; + char buf[IOSZ] __attribute__((aligned(IOSZ))); + + fd =tst_creat_unlinked (MNTPOINT ); + nfd =tst_creat_unlinked (NORMAL_PATH ); + p =SAFE_MMAP (NULL , hpage_size,PROT_READ |PROT_WRITE ,MAP_PRIVATE , fd,0 ); +memcpy (p,P0 ,8 ); + +SAFE_WRITE (1 , nfd, p,IOSZ ); +SAFE_LSEEK (nfd,0 ,SEEK_SET ); + +SAFE_READ (1 , nfd, buf,IOSZ ); +if (memcmp (P0 , buf,8 )) { +tst_res (TFAIL ,"Memory mismatch after Direct-IO write" ); + goto cleanup;testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c line 59
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap11.c new file +10
-0+ } +SAFE_LSEEK (nfd,0 ,SEEK_SET ); + +memset (p,0 ,IOSZ ); +SAFE_READ (1 , nfd, p,IOSZ ); + +if (memcmp (p,P0 ,8 )) +tst_res (TFAIL ,"Memory mismatch after Direct-IO read" ); +else +tst_res (TPASS ,"Successful" );^
We shoudl write something more meaningful. Something as:
Quoted 4 lines
"All data were read and written correctly"
Other than this the rest looks good.
Ok, Will update it.
Quoted 7 lines
Signature · 6 lines
-- Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
PATCH v2 3/5 Hugetlb: Migrating libhugetlbfs fadvise_reserve
In reply to Tarun SahuMigrating the libhugetlbfs/testcases/fadvise_reserve.c test
Test Description: fadvise() on some kernels can cause the reservation counter to get corrupted. The problem is that the patches are allocated for the reservation but not faulted in at the time of allocation. The counters do not get updated and effectively "leak". This test identifies whether the kernel is vulnerable to the problem or not. It's fixed in kernel by 'commit f2deae9d4e70 ("Remove implementation of readpage from the hugetlbfs_aops")'
--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugemmap/hugemmap12.c | 93 +++++++++++++++++++ 3 files changed, 95 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c
runtest/hugetlb +1 -0
@@ -8,6 +8,7 @@ hugemmap08 hugemmap08 hugemmap09 hugemmap09 hugemmap10 hugemmap10 hugemmap11 hugemmap11 +hugemmap12 hugemmap12 hugemmap05_1 hugemmap05 -m hugemmap05_2 hugemmap05 -s hugemmap05_3 hugemmap05 -s -m
testcases/kernel/mem/.gitignore +1 -0
@@ -9,6 +9,7 @@ /hugetlb/hugemmap/hugemmap09 /hugetlb/hugemmap/hugemmap10 /hugetlb/hugemmap/hugemmap11 +/hugetlb/hugemmap/hugemmap12 /hugetlb/hugeshmat/hugeshmat01 /hugetlb/hugeshmat/hugeshmat02 /hugetlb/hugeshmat/hugeshmat03
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +93 -0
93 lines not on this page · raw message
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 3/5] Hugetlb: Migrating libhugetlbfs fadvise_reserve
Hi!
Quoted 33 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +33
-0+/*\ +* [Description] +* +* fadvise() on some kernels can cause the reservation counter to get +* corrupted. The problem is that the patches are allocated for the +* reservation but not faulted in at the time of allocation. The counters +* do not get updated and effectively "leak". This test identifies whether +* the kernel is vulnerable to the problem or not. It's fixed in kernel +* by commit f2deae9d4e70793568ef9e85d227abb7bef5b622. +*/ + +#define _GNU_SOURCE +#include <stdio.h> +#include <sys/mount.h> +#include <limits.h> +#include <sys/param.h> +#include <sys/types.h> + +#include "hugetlb.h" + +#define MNTPOINT "hugetlbfs/" +static long hpage_size; +static int fd =-1 ; + +static void run_test (void ) +{ +void *p; +unsigned long initial_rsvd, map_rsvd, fadvise_rsvd, end_rsvd; + + fd =tst_creat_unlinked (MNTPOINT ); + + initial_rsvd =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); +tst_res (TINFO ,"Reserve count before map: %lu" , initial_rsvd);
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c line 50
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +10
-0+ + p =SAFE_MMAP (NULL , hpage_size,PROT_READ |PROT_WRITE ,MAP_SHARED , + fd,0 ); + map_rsvd =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); +tst_res (TINFO ,"Reserve count after map: %lu" , map_rsvd); + +if (posix_fadvise (fd,0 , hpage_size,POSIX_FADV_WILLNEED ) ==-1 ) { +tst_res (TFAIL |TERRNO ,"fadvise()" ); + goto cleanup; + }
If we follow how SAFE_MACROS() works this should rather be:
if (posix_fadvise(...) tst_brk(TBROK|TERRNO, "fadvise()");
Quoted 23 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +23
-0+ fadvise_rsvd =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); +tst_res (TINFO ,"Reserve count after fadvise: %lu" , fadvise_rsvd); + +memset (p,1 , hpage_size); + +SAFE_MUNMAP (p, hpage_size); + p =NULL ; +SAFE_CLOSE (fd); + end_rsvd =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); +tst_res (TINFO ,"Reserve count after close: %lu" , end_rsvd); + +TST_EXP_EQ_LU (end_rsvd, initial_rsvd); +cleanup: +if (p) +SAFE_MUNMAP (p, hpage_size); +if (fd >0 ) +SAFE_CLOSE (fd); +} + +static void setup (void ) +{ + hpage_size =SAFE_READ_MEMINFO (MEMINFO_HPAGE_SIZE )*1024 ; +}
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c line 83
Quoted 10 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +10
-0+ +static void cleanup (void ) +{ +if (fd >0 ) +SAFE_CLOSE (fd); +} + +static struct tst_test test = { + .tags = (struct tst_tag []) { + {"linux-git" ,"f2deae9d4e70793568ef9e85d227abb7bef5b622" },
We usually shorten the hash to first 12 characters however things should work fine either way.
Quoted 13 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +10
-0+ {} + }, + .needs_root = 1, + .mntpoint = MNTPOINT, + .needs_hugetlbfs = 1, + .setup = setup, + .cleanup = cleanup, + .test_all = run_test, + .hugepages = {1, TST_NEEDS}, +};Signature · 1 line
2.31.1
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 3/5] Hugetlb: Migrating libhugetlbfs fadvise_reserve
On Nov 09 2022, Cyril Hrubis wrote:
Hi,
--skip
Quoted 11 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c line 50
Quoted 5 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +5
-0+ +if (posix_fadvise (fd,0 , hpage_size,POSIX_FADV_WILLNEED ) ==-1 ) { +tst_res (TFAIL |TERRNO ,"fadvise()" ); + goto cleanup; + }If we follow how
SAFE_MACROS()works this should rather be:if (posix_fadvise(...) tst_brk(TBROK|TERRNO, "fadvise()");
Yes. I am thinking of adding it to tst_safe_macros (SAFE_POSIX_FADVISE). But there are other tests, that uses it raw
(https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/mincore/mincore04.c).
Was there any reason to not create a SAFE_MACROS for it?
Quoted 12 lines
Quoted 5 lines
testcases/kernel/mem/hugetlb/hugemmap/hugemmap12.c new file +2
-0+ fadvise_rsvd =SAFE_READ_MEMINFO (MEMINFO_HPAGE_RSVD ); +tst_res (TINFO ,"Reserve count after fadvise: %lu" , fadvise_rsvd);Signature · 1 line
2.31.1Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
Signature · 1 line
Mailing list info: https://lists.linux.it/listinfo/ltp
Re: [LTP] [PATCH v2 3/5] Hugetlb: Migrating libhugetlbfs fadvise_reserve
Hi!
Quoted 4 lines
Yes. I am thinking of adding it to
tst_safe_macros(SAFE_POSIX_FADVISE). But there are other tests, that uses it raw
(https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/mincore/mincore04.c).
Was there any reason to not create aSAFE_MACROSfor it?
I do not think so, we started adding safe macros for the most common calls and slowly moved to the less common. There are still plenty of calls that should have been added and tests converted to use them.
Signature · 5 lines
Cyril Hrubis [email protected] -- Mailing list info: https://lists.linux.it/listinfo/ltp
PATCH v2 4/5 Hugetlb: Migrating libhugetlbfs fallocate_align
In reply to Tarun SahuMigrating the libhugetlbfs/testcases/fallocate_align.c test
Test Description: It tests alignment of fallocate arguments. fallocate will take non-huge page aligned offsets and addresses. However, operations are only performed on huge pages. This is different that than fallocate behavior in "normal" filesystems.
--- runtest/hugetlb | 2 + testcases/kernel/mem/.gitignore | 1 + .../kernel/mem/hugetlb/hugefallocate/Makefile | 10 ++ .../hugetlb/hugefallocate/hugefallocate01.c | 169 ++++++++++++++++++ 4 files changed, 182 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/Makefile create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate01.c
runtest/hugetlb +2 -0
@@ -1,3 +1,5 @@ +hugefallocate01 hugefallocate01 + hugemmap01 hugemmap01 hugemmap02 hugemmap02 hugemmap04 hugemmap04
testcases/kernel/mem/.gitignore +1 -0
@@ -1,4 +1,5 @@ /cpuset/cpuset01 +/hugetlb/hugefallocate/hugefallocate01 /hugetlb/hugemmap/hugemmap01 /hugetlb/hugemmap/hugemmap02 /hugetlb/hugemmap/hugemmap04
testcases/kernel/mem/hugetlb/hugefallocate/Makefile new file +10 -0
@@ -0,0 +1,10 @@ +# SPDX-License-Identifier: GPL-2.0-or-later +# Copyright (C) 2009, Cisco Systems Inc. +# Ngie Cooper, July 2009 + +top_srcdir ?= ../../../../.. + +include $(top_srcdir)/include/mk/testcases.mk +include $(abs_srcdir)/../Makefile.inc +include $(top_srcdir)/include/mk/generic_leaf_target.mk +
testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate01.c new file +169 -0
169 lines not on this page · raw message
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp
PATCH v2 5/5 Hugetlb: Migrating libhugetlbfs fallocate_basic
In reply to Tarun SahuMigrating the libhugetlbfs/testcases/fallocate_basic.c test
Test Description: It tests basic fallocate functionality in hugetlbfs. Preallocate huge pages to a file in hugetlbfs, and then remove the pages via hole punch.
--- runtest/hugetlb | 1 + testcases/kernel/mem/.gitignore | 1 + .../hugetlb/hugefallocate/hugefallocate02.c | 90 +++++++++++++++++++ 3 files changed, 92 insertions(+) create mode 100644 testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate02.c
runtest/hugetlb +1 -0
@@ -1,4 +1,5 @@ hugefallocate01 hugefallocate01 +hugefallocate02 hugefallocate02 hugemmap01 hugemmap01 hugemmap02 hugemmap02
testcases/kernel/mem/.gitignore +1 -0
@@ -1,5 +1,6 @@ /cpuset/cpuset01 /hugetlb/hugefallocate/hugefallocate01 +/hugetlb/hugefallocate/hugefallocate02 /hugetlb/hugemmap/hugemmap01 /hugetlb/hugemmap/hugemmap02 /hugetlb/hugemmap/hugemmap04
testcases/kernel/mem/hugetlb/hugefallocate/hugefallocate02.c new file +90 -0
90 lines not on this page · raw message
Signature · 5 lines
2.31.1 -- Mailing list info: https://lists.linux.it/listinfo/ltp