From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: npiggin@gmail.com, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/5] Update hash MMU kernel mapping to be in sync with radix.
Date: Sun, 17 Mar 2019 21:18:22 +0530 [thread overview]
Message-ID: <20190317154827.9188-1-aneesh.kumar@linux.ibm.com> (raw)
This patch series map all the kernel regions (vmalloc, IO and vmemmap) using
0xc top nibble address. This brings hash translation kernel mapping in sync with radix.
Each of these regions can now map 512TB. We use one context to map these
regions and hence the 512TB limit. We also update radix to use the same limit even though
we don't have context related restrictions there.
Aneesh Kumar K.V (5):
powerpc/mm/hash64: Add a variable to track the end of IO mapping
powerpc/mm/hash64: Map all the kernel regions in the same 0xc range
powerpc/mm: Validate address values against different region limits
powerpc/mm: Drop the unnecessary region check
powerpc/mm/hash: Simplify the region id calculation.
arch/powerpc/include/asm/book3s/64/hash-4k.h | 15 +++
arch/powerpc/include/asm/book3s/64/hash-64k.h | 12 +++
arch/powerpc/include/asm/book3s/64/hash.h | 97 ++++++++++++-------
arch/powerpc/include/asm/book3s/64/mmu-hash.h | 31 +++---
arch/powerpc/include/asm/book3s/64/pgtable.h | 9 +-
arch/powerpc/include/asm/book3s/64/radix.h | 40 ++++----
arch/powerpc/include/asm/page.h | 11 ---
arch/powerpc/kvm/book3s_hv_rm_xics.c | 2 +-
arch/powerpc/mm/copro_fault.c | 14 ++-
arch/powerpc/mm/hash_utils_64.c | 45 ++++++---
arch/powerpc/mm/pgtable-hash64.c | 13 ++-
arch/powerpc/mm/pgtable-radix.c | 20 +++-
arch/powerpc/mm/pgtable_64.c | 9 +-
arch/powerpc/mm/ptdump/hashpagetable.c | 2 +-
arch/powerpc/mm/ptdump/ptdump.c | 3 +-
arch/powerpc/mm/slb.c | 22 +++--
arch/powerpc/platforms/cell/spu_base.c | 4 +-
drivers/misc/cxl/fault.c | 2 +-
drivers/misc/ocxl/link.c | 2 +-
19 files changed, 227 insertions(+), 126 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-17 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 15:48 Aneesh Kumar K.V [this message]
2019-03-17 15:48 ` [PATCH v2 1/5] powerpc/mm/hash64: Add a variable to track the end of IO mapping Aneesh Kumar K.V
2019-03-17 15:48 ` [PATCH v2 2/5] powerpc/mm/hash64: Map all the kernel regions in the same 0xc range Aneesh Kumar K.V
2019-03-17 15:48 ` [PATCH v2 3/5] powerpc/mm: Validate address values against different region limits Aneesh Kumar K.V
2019-03-17 15:48 ` [PATCH v2 4/5] powerpc/mm: Drop the unnecessary region check Aneesh Kumar K.V
2019-03-17 15:48 ` [PATCH v2 5/5] powerpc/mm/hash: Simplify the region id calculation 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=20190317154827.9188-1-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--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).