Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-20 Thread Mark Salter
On Thu, 2014-06-19 at 21:24 +0200, Michal Nazarewicz wrote: > On Thu, Jun 19 2014, Mark Salter wrote: > > On Tue, 2014-06-17 at 20:32 +0200, Michal Nazarewicz wrote: > >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c > >> index 5dba293..6e657ce 100644 > >> --- a/mm/page_alloc.c > >> +++ b/mm/page

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-19 Thread Michal Nazarewicz
On Thu, Jun 19 2014, Mark Salter wrote: > On Tue, 2014-06-17 at 20:32 +0200, Michal Nazarewicz wrote: >> diff --git a/mm/page_alloc.c b/mm/page_alloc.c >> index 5dba293..6e657ce 100644 >> --- a/mm/page_alloc.c >> +++ b/mm/page_alloc.c >> @@ -801,7 +801,15 @@ void __init init_cma_reserved_pageblock

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-19 Thread Mark Salter
On Tue, 2014-06-17 at 20:32 +0200, Michal Nazarewicz wrote: > On Wed, Jun 11 2014, David Rientjes wrote: > > On Wed, 11 Jun 2014, Mark Salter wrote: > > > >> With a kernel configured with ARM64_64K_PAGES && !TRANSPARENT_HUGEPAGE > >> I get this at early boot: > >> > >> SMP: Total of 8 processors

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-17 Thread Michal Nazarewicz
On Wed, Jun 11 2014, David Rientjes wrote: > On Wed, 11 Jun 2014, Mark Salter wrote: > >> With a kernel configured with ARM64_64K_PAGES && !TRANSPARENT_HUGEPAGE >> I get this at early boot: >> >> SMP: Total of 8 processors activated. >> devtmpfs: initialized >> Unable to handle kernel NULL p

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-12 Thread Mark Salter
On Wed, 2014-06-11 at 16:04 -0700, David Rientjes wrote: > On Wed, 11 Jun 2014, David Rientjes wrote: > > > Any reason to not switch this to > > > > ARM64_64K_PAGES && TRANSPARENT_HUGEPAGE && CMA > > > > (ARM64_64K_PAGES) && (TRANSPARENT_HUGEPAGE || CMA) And add HUGETLB to the list also? I

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-11 Thread David Rientjes
On Wed, 11 Jun 2014, David Rientjes wrote: > Any reason to not switch this to > > ARM64_64K_PAGES && TRANSPARENT_HUGEPAGE && CMA > (ARM64_64K_PAGES) && (TRANSPARENT_HUGEPAGE || CMA) > instead? If pageblock_order > MAX_ORDER because of > HPAGE_SHIFT > PAGE_SHIFT, then cma is always goin

Re: [PATCH] arm64: fix MAX_ORDER for 64K pagesize

2014-06-11 Thread David Rientjes
On Wed, 11 Jun 2014, Mark Salter wrote: > With a kernel configured with ARM64_64K_PAGES && !TRANSPARENT_HUGEPAGE > I get this at early boot: > > SMP: Total of 8 processors activated. > devtmpfs: initialized > Unable to handle kernel NULL pointer dereference at virtual address 0008 > p