From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 3/3] hugemmap34: Test to detect bug with migrating gigantic pages
Date: Fri, 16 Feb 2024 13:01:20 +0100 [thread overview]
Message-ID: <20240216120120.GB903763@pevik> (raw)
In-Reply-To: <20231106093031.1844129-4-liwang@redhat.com>
Hi Li,
FYI hugemmap34 fails on x86_64 and s390x various SLES kernels (tested: x86_64
from 4.4 to 6.4, s390x from 4.12. to 6.4):
tst_test.c:1627: TINFO: Timeout per run is 0h 01m 30s
hugemmap34.c:85: TBROK: mmap() failed: EINVAL (22)
Removing MAP_HUGE_1GB shows TBROK due ENOMEM.
I suppose low memory resource for this VM.
=> Maybe we need .min_mem_avail = 1024?
+ define the value and reuse also here (so that we don't forget to update on
other place if later changed):
hugetlbsize = 1 * 1024 * 1024 * 1024u;
(also remove '1 *')
Although you do #include <linux/mman.h>, for some reason I get some failures on
aarch64 and s390x on old gcc 4.8.5:
hugemmap34.c:82:39: error: ‘MAP_HUGE_1GB’ undeclared (first use in this function)
MAP_PRIVATE|MAP_ANON|MAP_HUGETLB|MAP_HUGE_1GB,
^
But works on the same toolchain with gcc 7.5.0, also x86_64 and ppc64le works
fine on them). It looks to me MAP_HUGE_1GB will need to be backported to lapi.
It works on x86_64 and ppc64le.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-02-16 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 9:30 [LTP] [PATCH v3 0/3] Introduce new field .hptype for reserving gigantic page Li Wang
2023-11-06 9:30 ` [LTP] [PATCH v3 1/3] lib: add support for kinds of hpsize reservation Li Wang
2024-02-16 11:22 ` Petr Vorel
2023-11-06 9:30 ` [LTP] [PATCH v3 2/3] hugemmap32: improvement test Li Wang
2024-02-16 12:09 ` Petr Vorel
2023-11-06 9:30 ` [LTP] [PATCH v3 3/3] hugemmap34: Test to detect bug with migrating gigantic pages Li Wang
2024-02-16 12:01 ` Petr Vorel [this message]
2024-02-16 12:12 ` Petr Vorel
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=20240216120120.GB903763@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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.