From: shijie.huang@arm.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] mm: fix the "counter.sh" failure for libhugetlbfs
Date: Thu, 3 Nov 2016 10:51:36 +0800 [thread overview]
Message-ID: <1478141499-13825-1-git-send-email-shijie.huang@arm.com> (raw)
(1) Background
For the arm64, the hugetlb page size can be 32M (PMD + Contiguous bit).
In the 4K page environment, the max page order is 10 (max_order - 1),
so 32M page is the gigantic page.
The arm64 MMU supports a Contiguous bit which is a hint that the TTE
is one of a set of contiguous entries which can be cached in a single
TLB entry. Please refer to the arm64v8 mannul :
DDI0487A_f_armv8_arm.pdf (in page D4-1811)
(2) The bug
After I tested the libhugetlbfs, I found the test case "counter.sh"
will fail with the gigantic page (32M page in arm64 board).
This patch set adds support for gigantic surplus hugetlb pages,
allowing the counter.sh unit test to pass.
Huang Shijie (2):
mm: hugetlb: rename some allocation functions
mm: hugetlb: support gigantic surplus pages
mm/hugetlb.c | 35 ++++++++++++++++++++---------------
1 file changed, 20 insertions(+), 15 deletions(-)
--
2.1.4
next reply other threads:[~2016-11-03 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 2:51 Huang Shijie [this message]
2016-11-03 2:51 ` [PATCH 1/2] mm: hugetlb: rename some allocation functions Huang Shijie
2016-11-04 3:11 ` [PATCH] " Huang Shijie
2016-11-03 2:51 ` [PATCH 2/2] mm: hugetlb: support gigantic surplus pages Huang Shijie
2016-11-03 3:13 ` kbuild test robot
2016-11-07 15:25 ` Gerald Schaefer
2016-11-08 2:19 ` Huang Shijie
2016-11-08 7:08 ` Huang Shijie
2016-11-08 9:17 ` Huang Shijie
2016-11-08 19:27 ` Gerald Schaefer
2016-11-09 7:12 ` Huang Shijie
2016-11-09 7:08 ` [PATCH v2 " Huang Shijie
2016-11-09 15:55 ` Gerald Schaefer
2016-11-10 7:03 ` Huang Shijie
2016-11-03 17:22 ` [PATCH 0/2] mm: fix the "counter.sh" failure for libhugetlbfs Randy Dunlap
2016-11-04 1:59 ` Huang Shijie
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=1478141499-13825-1-git-send-email-shijie.huang@arm.com \
--to=shijie.huang@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).