linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: npiggin@gmail.com, paulus@samba.org, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 2/8] powerpc/mm/hash64: Map all the kernel regions in the same 0xc range
Date: Thu, 18 Apr 2019 09:17:24 +0530	[thread overview]
Message-ID: <52d533ea-b9c4-e0c8-d7eb-719d1b05028a@linux.ibm.com> (raw)
In-Reply-To: <20190417125920.785-3-aneesh.kumar@linux.ibm.com>

On 4/17/19 6:29 PM, Aneesh Kumar K.V wrote:
> This patch maps vmalloc, IO and vmemap regions in the 0xc address range
> instead of the current 0xd and 0xf range. This brings the mapping closer
> to radix translation mode.
> 
> With hash 64K page size each of this region is 512TB whereas with 4K config
> we are limited by the max page table range of 64TB and hence there regions
> are of 16TB size.
> 
> The kernel mapping is now:
> 
>   On 4K hash
> 
>       kernel_region_map_size = 16TB
>       kernel vmalloc start   = 0xc000100000000000
>       kernel IO start        = 0xc000200000000000
>       kernel vmemmap start   = 0xc000300000000000
> 
> 64K hash, 64K radix and 4k radix:
> 
>       kernel_region_map_size = 512TB
>       kernel vmalloc start   = 0xc008000000000000
>       kernel IO start        = 0xc00a000000000000
>       kernel vmemmap start   = 0xc00c000000000000

I missed this when sending out the patch.

diff --git a/arch/powerpc/mm/pgtable-radix.c 
b/arch/powerpc/mm/pgtable-radix.c
index 263c3ff662c3..30fc0909f1d8 100644
--- a/arch/powerpc/mm/pgtable-radix.c
+++ b/arch/powerpc/mm/pgtable-radix.c
@@ -136,7 +136,7 @@ static int __map_kernel_page(unsigned long ea, 
unsigned long pa,
         BUILD_BUG_ON(TASK_SIZE_USER64 > RADIX_PGTABLE_RANGE);

  #ifdef CONFIG_PPC_64K_PAGES
-       BUILD_BUG_ON(RADIX_KERN_MAP_SIZE != MAX_EA_BITS_PER_CONTEXT);
+       BUILD_BUG_ON(RADIX_KERN_MAP_SIZE != (1UL << 
MAX_EA_BITS_PER_CONTEXT));
  #endif

         if (unlikely(!slab_is_available()))




  parent reply	other threads:[~2019-04-18  3:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 12:59 [PATCH v4 0/8] Update hash MMU kernel mapping to be in sync with radix Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 1/8] powerpc/mm/hash64: Add a variable to track the end of IO mapping Aneesh Kumar K.V
2019-04-21 14:19   ` [v4, " Michael Ellerman
2019-04-17 12:59 ` [PATCH v4 2/8] powerpc/mm/hash64: Map all the kernel regions in the same 0xc range Aneesh Kumar K.V
2019-04-17 22:27   ` kbuild test robot
2019-04-18  3:47   ` Aneesh Kumar K.V [this message]
2019-04-17 12:59 ` [PATCH v4 3/8] powerpc/mm: Validate address values against different region limits Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 4/8] powerpc/mm: Drop the unnecessary region check Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 5/8] powerpc/mm/hash: Simplify the region id calculation Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 6/8] powerpc/mm: Print kernel map details to dmesg Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 7/8] powerpc/mm/hash: Rename KERNEL_REGION_ID to LINEAR_MAP_REGION_ID Aneesh Kumar K.V
2019-04-17 12:59 ` [PATCH v4 8/8] powerpc/mm/hash/4K: Update the vmalloc start for hash 4K config Aneesh Kumar K.V

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=52d533ea-b9c4-e0c8-d7eb-719d1b05028a@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --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).