From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anthony Yznaga <anthony.yznaga@oracle.com>,
sparclinux@vger.kernel.org, davem@davemloft.net,
andreas@gaisler.com
Cc: linux-kernel@vger.kernel.org, agordeev@linux.ibm.com,
will@kernel.org, ryan.roberts@arm.com, david@redhat.com,
osalvador@suse.de
Subject: Re: [PATCH] sparc64: fix hugetlb for sun4u
Date: Fri, 25 Jul 2025 23:09:29 +0200 [thread overview]
Message-ID: <9a1fcf10fef8490875a179d33dcf99e08b0d71ce.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <75cd8cf5b1cddc0914d29df20d3f664efd173b3c.camel@physik.fu-berlin.de>
Hi again,
On Fri, 2025-07-25 at 22:46 +0200, John Paul Adrian Glaubitz wrote:
> slbpacaflush (8M: 64): Bad configuration: Atleast online 2 cpus are required
> straddle_4GB_static (8M: 64): PASS
> huge_at_4GB_normal_below_static (8M: 64): FAIL Wrong address with MAP_FIXED normal
> huge_below_4GB_normal_above_static (8M: 64): PASS
> map_high_truncate_2 (8M: 64): PASS
> misaligned_offset (8M: 64): PASS (inconclusive)
> truncate_above_4GB (8M: 64): PASS
> brk_near_huge (8M: 64): Fatal glibc error: malloc.c:2601 (sysmalloc): assertion failed:
> (...)
> fallocate_stress.sh (8M: 64): PASS
> ********** TEST SUMMARY
> * 8M
> * 32-bit 64-bit
> * Total testcases: 0 111
> * Skipped: 0 9
> * PASS: 0 57
> * FAIL: 0 1
> * Killed by signal: 0 1
> * Bad configuration: 0 4
> * Expected FAIL: 0 0
> * Unexpected PASS: 0 0
> * Test not present: 0 39
> * Strange test result: 0 0
> **********
> root@raverin:/home/glaubitz/libhugetlbfs#
>
> Tested-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Ah, I noticed that huge_at_4GB_normal_below_static fails.
Does that test require at least 4 GB of RAM? If yes, it's not surprising
the test fails as this machine have only 2 GB of physical memory and just
1 GB of swap space:
root@raverin:/home/glaubitz/libhugetlbfs# free -h
total used free shared buff/cache available
Mem: 2.0Gi 591Mi 896Mi 1.1Mi 792Mi 1.4Gi
Swap: 976Mi 3.0Mi 973Mi
root@raverin:/home/glaubitz/libhugetlbfs#
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2025-07-25 21:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 1:24 Anthony Yznaga
2025-07-16 6:18 ` John Paul Adrian Glaubitz
2025-07-16 8:41 ` John Paul Adrian Glaubitz
2025-07-16 16:47 ` Anthony Yznaga
2025-07-24 10:52 ` John Paul Adrian Glaubitz
2025-07-25 5:59 ` John Paul Adrian Glaubitz
2025-07-25 20:46 ` John Paul Adrian Glaubitz
2025-07-25 21:09 ` John Paul Adrian Glaubitz [this message]
2025-08-08 21:31 ` John Paul Adrian Glaubitz
2025-08-08 22:15 ` Anthony Yznaga
2025-08-08 22:37 ` John Paul Adrian Glaubitz
2025-08-09 6:23 ` John Paul Adrian Glaubitz
2025-08-09 6:26 ` John Paul Adrian Glaubitz
2025-08-09 6:42 ` John Paul Adrian Glaubitz
2025-08-10 9:52 ` John Paul Adrian Glaubitz
2025-08-10 22:20 ` John Paul Adrian Glaubitz
2025-08-11 8:25 ` David Hildenbrand
2025-08-11 10:44 ` John Paul Adrian Glaubitz
2025-08-11 11:06 ` John Paul Adrian Glaubitz
2025-08-12 12:32 ` Found it - was: " John Paul Adrian Glaubitz
2025-08-12 12:34 ` John Paul Adrian Glaubitz
2025-08-21 12:52 ` David Hildenbrand
2025-08-21 15:03 ` Edgecombe, Rick P
2025-08-21 16:42 ` John Paul Adrian Glaubitz
2025-08-11 8:20 ` David Hildenbrand
2025-08-11 8:28 ` John Paul Adrian Glaubitz
2025-09-19 18:01 ` Andreas Larsson
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=9a1fcf10fef8490875a179d33dcf99e08b0d71ce.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=agordeev@linux.ibm.com \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=ryan.roberts@arm.com \
--cc=sparclinux@vger.kernel.org \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®