From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 1/3] mm/hugetlb: Allow arch to override and call the weak function
Date: Thu, 27 Jul 2017 21:50:35 +0530 [thread overview]
Message-ID: <e963e910-1999-ddff-87cf-9e8c356fea82@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170727130123.GE27766@dhcp22.suse.cz>
On 07/27/2017 06:31 PM, Michal Hocko wrote:
> On Thu 27-07-17 11:48:26, Aneesh Kumar K.V wrote:
>> For ppc64, we want to call this function when we are not running as guest.
>
> What does this mean?
>
ppc64 guest (aka LPAR) support a different mechanism for hugetlb
allocation/reservation. The LPAR management application called HMC can
be used to reserve a set of hugepages and we pass the details of
reserved pages via device tree to the guest. You can find the details in
htab_dt_scan_hugepage_blocks() . We do the memblock_reserve of the range
and later in the boot sequence, we just add the reserved range to
huge_boot_pages.
For baremetal config (when we are not running as guest) we want to
follow what other architecture does, that is look at the command line
and do memblock allocation. Hence the need to call generic function
__alloc_bootmem_huge_page() in that case.
I can add all these details in to the commit message if that makes it easy ?
-aneesh
next prev parent reply other threads:[~2017-07-27 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 6:18 [PATCH v3 1/3] mm/hugetlb: Allow arch to override and call the weak function Aneesh Kumar K.V
2017-07-27 6:18 ` [PATCH v3 2/3] powerpc/mm/hugetlb: Add support for reserving gigantic huge pages via kernel command line Aneesh Kumar K.V
2017-07-27 6:18 ` [PATCH v3 3/3] powerpc/mm/hugetlb: Allow runtime allocation of 16G Aneesh Kumar K.V
2017-07-27 13:01 ` [PATCH v3 1/3] mm/hugetlb: Allow arch to override and call the weak function Michal Hocko
2017-07-27 16:20 ` Aneesh Kumar K.V [this message]
2017-07-28 7:06 ` Michal Hocko
2017-07-27 15:25 ` Liam R. Howlett
2017-07-27 16:12 ` Aneesh Kumar K.V
2017-07-27 17:38 ` Liam R. Howlett
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=e963e910-1999-ddff-87cf-9e8c356fea82@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).