From: santhosh <santhog4@linux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Rashmica Gupta <rashmicy@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Cc: manvanth@linux.vnet.ibm.com
Subject: Re: [V2] powerpc/Kconfig: Update config option based on page size.
Date: Wed, 14 Sep 2016 16:10:43 +0530 [thread overview]
Message-ID: <0d167ff1-cc0e-35bc-479c-aec77d2c8556@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y4893ar2.fsf@skywalker.in.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
> Michael Ellerman <mpe@ellerman.id.au> writes:
>
>> On Fri, 2016-19-02 at 05:38:47 UTC, Rashmica Gupta wrote:
>>> Currently on PPC64 changing kernel pagesize from 4K to 64K leaves
>>> FORCE_MAX_ZONEORDER set to 13 - which produces a compile error.
>>>
>> ...
>>> So, update the range of FORCE_MAX_ZONEORDER from 9-64 to 8-9 for 64K pages
>>> and from 13-64 to 9-13 for 4K pages.
>>>
>>> Signed-off-by: Rashmica Gupta <rashmicy@gmail.com>
>>> Reviewed-by: Balbir Singh <bsingharora@gmail.com>
>> Applied to powerpc next, thanks.
>>
>> https://git.kernel.org/powerpc/c/a7ee539584acf4a565b7439cea
>>
> HPAGE_PMD_ORDER is not something we should check w.r.t 4k linux page
> size. We do have the below constraint w.r.t hugetlb pages
>
> static inline bool hstate_is_gigantic(struct hstate *h)
> {
> return huge_page_order(h) >= MAX_ORDER;
> }
>
> That require MAX_ORDER to be greater than 12.
>
> Did we test hugetlbfs 4k config with this patch ? Will it work if we
> start marking hugepage as gigantic page ?
>
> -aneesh
>
Hello Rashmica,
With upstream linux kernel 4.8.0-rc1-00006-gbae9cc6 compiled with linux
4k page size we are not able set hugepages, Aneesh had a look at the
problem and he mentioned this commit is causing the issue.
*Details:*
We are using pkvm ubuntu 16.04 guest with upstream kernel
[4.8.0-rc1-00006-gbae9cc6] compiled with 4k page size
o/p from guest:
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 16384 kB
Page sizes from device-tree: [dmesg]
[ 0.000000] base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000,
tlbiel=1, penc=0
[ 0.000000] base_shift=12: shift=24, sllp=0x0000, avpnm=0x00000000,
tlbiel=1, penc=56
[ 0.000000] base_shift=24: shift=24, sllp=0x0100, avpnm=0x00000001,
tlbiel=0, penc=0
while trying to configure the hugepages inside the guest it throws the
below error:
echo 100 > /proc/sys/vm/nr_hugepages
-bash: echo: write error: Invalid argument
*Note*: we do not see the problem when the linux page is 64k
Thanks,
Santhosh G
[-- Attachment #2: Type: text/html, Size: 3279 bytes --]
next prev parent reply other threads:[~2016-09-14 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 5:38 [PATCH V2] powerpc/Kconfig: Update config option based on page size Rashmica Gupta
2016-02-19 6:07 ` Balbir Singh
2016-04-11 12:35 ` [V2] " Michael Ellerman
2016-04-19 14:59 ` Aneesh Kumar K.V
2016-04-19 23:09 ` Balbir Singh
2016-09-14 10:40 ` santhosh [this message]
2016-09-15 23:26 ` Michael Ellerman
2016-09-16 6:03 ` Balbir Singh
2016-09-16 15:16 ` Aneesh Kumar K.V
2016-09-19 7:15 ` Balbir Singh
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=0d167ff1-cc0e-35bc-479c-aec77d2c8556@linux.vnet.ibm.com \
--to=santhog4@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manvanth@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=rashmicy@gmail.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).