From: Balbir Singh <bsingharora@gmail.com>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>,
jk@ozlabs.org, Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stewart Smith <stewart@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, victora@br.ibm.com,
victora <victora@linux.vnet.ibm.com>,
alistair@popple.id.au
Subject: Re: 1M hugepage size being registered on Linux
Date: Thu, 22 Jun 2017 18:54:14 +1000 [thread overview]
Message-ID: <1498121654.7935.1.camel@gmail.com> (raw)
In-Reply-To: <3493fb6b-5212-843c-60b8-b2b715b52154@linux.vnet.ibm.com>
On Wed, 2017-06-21 at 12:32 -0300, Mauricio Faria de Oliveira wrote:
> 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? :- )
>
>
Aneesh changed the code to support just 16M and 16G hugepages for hash even
if the firmware exported that size. What is your end goal to support those
pages or to prevent them from being used?
Balbir Singh.
next prev parent reply other threads:[~2017-06-22 8:55 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
2017-06-22 8:54 ` Balbir Singh [this message]
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=1498121654.7935.1.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mauricfo@linux.vnet.ibm.com \
--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 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.