On Thu 27-07-17 21:50:35, Aneesh Kumar K.V wrote:
>
>
> 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) suppo
* Aneesh Kumar K.V [170727 12:12]:
>
>
> On 07/27/2017 08:55 PM, Liam R. Howlett wrote:
> > * Aneesh Kumar K.V [170727 02:18]:
> > > For ppc64, we want to call this function when we are not running as guest.
> > > Also, if we failed to allocate hugepages, let the user know.
> > >
> > [...]
> >
* Aneesh Kumar K.V [170727 02:18]:
> For ppc64, we want to call this function when we are not running as guest.
> Also, if we failed to allocate hugepages, let the user know.
>
[...]
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index bc48ee783dd9..a3a7a7e6339e 100644
> --- a/mm/hugetlb.c
> +++ b/
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
On 07/27/2017 08:55 PM, Liam R. Howlett wrote:
* Aneesh Kumar K.V [170727 02:18]:
For ppc64, we want to call this function when we are not running as guest.
Also, if we failed to allocate hugepages, let the user know.
[...]
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index bc48ee783dd9..a3a7a
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?
> Also, if we failed to allocate hugepages, let the user know.
>
> Signed-off-by: Aneesh Kumar K.V
> ---
> include/linux/hugetlb.h | 1 +
> mm/hug
For ppc64, we want to call this function when we are not running as guest.
Also, if we failed to allocate hugepages, let the user know.
Signed-off-by: Aneesh Kumar K.V
---
include/linux/hugetlb.h | 1 +
mm/hugetlb.c| 5 -
2 files changed, 5 insertions(+), 1 deletion(-)
diff --gi
