sh: Definitions for 3-level page table layout
authorMatt Fleming <matt@console-pimps.org>
Sun, 13 Dec 2009 14:38:50 +0000 (14:38 +0000)
committerPaul Mundt <lethal@linux-sh.org>
Thu, 17 Dec 2009 05:31:20 +0000 (14:31 +0900)
commit5d9b4b19f118abfb75e352841f7bf74580d7e427
tree5b9d0ec51bd12165d842d1d8a208e7568971757b
parentb73c806341cfc7492ede6a2ce713cb579547d0ab
sh: Definitions for 3-level page table layout

If using 64-bit PTEs and 4K pages then each page table has 512 entries
(as opposed to 1024 entries with 32-bit PTEs). Unlike MIPS, SH follows
the convention that all structures in the page table (pgd_t, pmd_t,
pgprot_t, etc) must be the same size. Therefore, 64-bit PTEs require
64-bit PGD entries, etc. Using 2-levels of page tables and 64-bit PTEs
it is only possible to map 1GB of virtual address space.

In order to map all 4GB of virtual address space we need to adopt a
3-level page table layout. This actually works out better for
CONFIG_SUPERH32 because we only waste 2 PGD entries on the P1 and P2
areas (which are untranslated) instead of 256.

Signed-off-by: Matt Fleming <matt@console-pimps.org>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
arch/sh/include/asm/pgalloc.h
arch/sh/include/asm/pgalloc_pmd.h [new file with mode: 0644]
arch/sh/include/asm/pgtable.h
arch/sh/include/asm/pgtable_pmd.h [new file with mode: 0644]
arch/sh/mm/Kconfig
arch/sh/mm/fault_32.c
arch/sh/mm/init.c