From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: jk@ozlabs.org, Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stewart Smith <stewart@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
victora <victora@linux.vnet.ibm.com>,
alistair@popple.id.au, victora@br.ibm.com,
linuxppc-dev@ozlabs.org
Subject: Re: 1M hugepage size being registered on Linux
Date: Wed, 21 Jun 2017 12:32:11 -0300 [thread overview]
Message-ID: <3493fb6b-5212-843c-60b8-b2b715b52154@linux.vnet.ibm.com> (raw)
In-Reply-To: <87wp85sk9o.fsf@concordia.ellerman.id.au>
On 06/21/2017 07:33 AM, Michael Ellerman wrote:
>> I am working on a bug related to 1M hugepage size being registered on
>> Linux (Power 8 Baremetal - Garrison).
> Wasn't that caused by a firmware bug?
Ben/Stewart, does that ring a bell, something new, intended or not? :- )
Thanks,
>> I was checking dmesg and it seems that 1M page size is coming from
>> firmware to Linux.
>>
>> [ 0.000000] base_shift=20: shift=20, sllp=0x0130, avpnm=0x00000000,
>> tlbiel=0, penc=2
>> [ 1.528867] HugeTLB registered 1 MB page size, pre-allocated 0 pages
>>
>> Should Linux support this page size?
> Does it work?:)
>
> The user manual says it's a supported size, but I thought it didn't work
> (in hardware) for some reason.
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2017-06-21 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 13:47 1M hugepage size being registered on Linux victora
2017-06-21 10:33 ` Michael Ellerman
2017-06-21 15:32 ` Mauricio Faria de Oliveira [this message]
2017-06-22 8:54 ` Balbir Singh
2017-06-22 8:21 ` Benjamin Herrenschmidt
2017-06-22 3:59 ` Michael Ellerman
2017-06-22 8:09 ` Benjamin Herrenschmidt
2017-06-22 11:17 ` Michael Ellerman
2017-06-23 19:00 ` victora
2017-06-26 3:14 ` Michael Ellerman
2017-06-22 11:03 ` Michal Suchánek
2017-06-23 5:26 ` Michael Ellerman
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=3493fb6b-5212-843c-60b8-b2b715b52154@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stewart@linux.vnet.ibm.com \
--cc=victora@br.ibm.com \
--cc=victora@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).