1 Memory Layout on AArch64 Linux
2 ==============================
4 Author: Catalin Marinas <catalin.marinas@arm.com>
5 Date : 20 February 2012
7 This document describes the virtual memory layout used by the AArch64
8 Linux kernel. The architecture allows up to 4 levels of translation
9 tables with a 4KB page size and up to 3 levels with a 64KB page size.
11 AArch64 Linux uses 3 levels of translation tables with the 4KB page
12 configuration, allowing 39-bit (512GB) virtual addresses for both user
13 and kernel. With 64KB pages, only 2 levels of translation tables are
14 used but the memory layout is the same.
16 User addresses have bits 63:39 set to 0 while the kernel addresses have
17 the same bits set to 1. TTBRx selection is given by bit 63 of the
18 virtual address. The swapper_pg_dir contains only kernel (global)
19 mappings while the user pgd contains only user (non-global) mappings.
20 The swapper_pgd_dir address is written to TTBR1 and never written to
24 AArch64 Linux memory layout with 4KB pages:
27 -----------------------------------------------------------------------
28 0000000000000000 0000007fffffffff 512GB user
30 ffffff8000000000 ffffffbbfffeffff ~240GB vmalloc
32 ffffffbbffff0000 ffffffbbffffffff 64KB [guard page]
34 ffffffbc00000000 ffffffbdffffffff 8GB vmemmap
36 ffffffbe00000000 ffffffbffbbfffff ~8GB [guard, future vmmemap]
38 ffffffbffa000000 ffffffbffaffffff 16MB PCI I/O space
40 ffffffbffb000000 ffffffbffbbfffff 12MB [guard]
42 ffffffbffbc00000 ffffffbffbdfffff 2MB fixed mappings
44 ffffffbffbe00000 ffffffbffbffffff 2MB [guard]
46 ffffffbffc000000 ffffffbfffffffff 64MB modules
48 ffffffc000000000 ffffffffffffffff 256GB kernel logical memory map
51 AArch64 Linux memory layout with 64KB pages:
54 -----------------------------------------------------------------------
55 0000000000000000 000003ffffffffff 4TB user
57 fffffc0000000000 fffffdfbfffeffff ~2TB vmalloc
59 fffffdfbffff0000 fffffdfbffffffff 64KB [guard page]
61 fffffdfc00000000 fffffdfdffffffff 8GB vmemmap
63 fffffdfe00000000 fffffdfffbbfffff ~8GB [guard, future vmmemap]
65 fffffdfffa000000 fffffdfffaffffff 16MB PCI I/O space
67 fffffdfffb000000 fffffdfffbbfffff 12MB [guard]
69 fffffdfffbc00000 fffffdfffbdfffff 2MB fixed mappings
71 fffffdfffbe00000 fffffdfffbffffff 2MB [guard]
73 fffffdfffc000000 fffffdffffffffff 64MB modules
75 fffffe0000000000 ffffffffffffffff 2TB kernel logical memory map
78 Translation table lookup with 4KB pages:
80 +--------+--------+--------+--------+--------+--------+--------+--------+
81 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
82 +--------+--------+--------+--------+--------+--------+--------+--------+
85 | | | | | [11:0] in-page offset
86 | | | | +-> [20:12] L3 index
87 | | | +-----------> [29:21] L2 index
88 | | +---------------------> [38:30] L1 index
89 | +-------------------------------> [47:39] L0 index (not used)
90 +-------------------------------------------------> [63] TTBR0/1
93 Translation table lookup with 64KB pages:
95 +--------+--------+--------+--------+--------+--------+--------+--------+
96 |63 56|55 48|47 40|39 32|31 24|23 16|15 8|7 0|
97 +--------+--------+--------+--------+--------+--------+--------+--------+
100 | | | | [15:0] in-page offset
101 | | | +----------> [28:16] L3 index
102 | | +--------------------------> [41:29] L2 index (only 38:29 used)
103 | +-------------------------------> [47:42] L1 index (not used)
104 +-------------------------------------------------> [63] TTBR0/1
106 When using KVM, the hypervisor maps kernel pages in EL2, at a fixed
107 offset from the kernel VA (top 24bits of the kernel VA set to zero):
110 -----------------------------------------------------------------------
111 0000004000000000 0000007fffffffff 256GB kernel objects mapped in HYP