Lines Matching +full:non +full:- +full:overlap +full:- +full:time
1 .. SPDX-License-Identifier: GPL-2.0
7 Complete virtual memory map with 4-level page tables
12 - Negative addresses such as "-23 TB" are absolute addresses in bytes, counted down
13 from the top of the 64-bit address space. It's easier to understand the layout
14 when seen both in absolute addresses and in distance-from-top notation.
16 For example 0xffffe90000000000 == -23 TB, it's 23 TB lower than the top of the
17 64-bit address space (ffffffffffffffff).
22 - "16M TB" might look weird at first sight, but it's an easier way to visualize size
24 It also shows it nicely how incredibly large 64-bit address space is.
32 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
35 …000 | +128 TB | ffff7fffffffffff | ~16M TB | ... huge, almost 64 bits wide hole of non-canonical
36 … | | | | virtual memory addresses up to the -128 TB
40 … | Kernel-space virtual memory, shared between all processes:
43 …ffff800000000000 | -128 TB | ffff87ffffffffff | 8 TB | ... guard hole, also reserved for hyp…
44 ffff880000000000 | -120 TB | ffff887fffffffff | 0.5 TB | LDT remap for PTI
45 …ffff888000000000 | -119.5 TB | ffffc87fffffffff | 64 TB | direct mapping of all physical memory…
46 ffffc88000000000 | -55.5 TB | ffffc8ffffffffff | 0.5 TB | ... unused hole
47 ffffc90000000000 | -55 TB | ffffe8ffffffffff | 32 TB | vmalloc/ioremap space (vmalloc_base)
48 ffffe90000000000 | -23 TB | ffffe9ffffffffff | 1 TB | ... unused hole
49 ffffea0000000000 | -22 TB | ffffeaffffffffff | 1 TB | virtual memory map (vmemmap_base)
50 ffffeb0000000000 | -21 TB | ffffebffffffffff | 1 TB | ... unused hole
51 ffffec0000000000 | -20 TB | fffffbffffffffff | 16 TB | KASAN shadow memory
54 … | Identical layout to the 56-bit one from here on:
57 fffffc0000000000 | -4 TB | fffffdffffffffff | 2 TB | ... unused hole
59 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
60 fffffe8000000000 | -1.5 TB | fffffeffffffffff | 0.5 TB | ... unused hole
61 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks
62 ffffff8000000000 | -512 GB | ffffffeeffffffff | 444 GB | ... unused hole
63 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
64 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | ... unused hole
65 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
66 ffffffff80000000 |-2048 MB | | |
67 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
68 ffffffffff000000 | -16 MB | | |
69 …FIXADDR_START | ~-11 MB | ffffffffff5fffff | ~0.5 MB | kernel-internal fixmap range, variable s…
70 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
71 ffffffffffe00000 | -2 MB | ffffffffffffffff | 2 MB | ... unused hole
75 Complete virtual memory map with 5-level page tables
80 - With 56-bit addresses, user-space memory gets expanded by a factor of 512x,
81 from 0.125 PB to 64 PB. All kernel mappings shift down to the -64 PB starting
91 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
94 … +64 PB | feffffffffffffff | ~16K PB | ... huge, still almost 64 bits wide hole of non-canonical
95 … | | | | virtual memory addresses up to the -64 PB
99 … | Kernel-space virtual memory, shared between all processes:
102 …ff00000000000000 | -64 PB | ff0fffffffffffff | 4 PB | ... guard hole, also reserved for hyp…
103 ff10000000000000 | -60 PB | ff10ffffffffffff | 0.25 PB | LDT remap for PTI
104 …ff11000000000000 | -59.75 PB | ff90ffffffffffff | 32 PB | direct mapping of all physical memory…
105 ff91000000000000 | -27.75 PB | ff9fffffffffffff | 3.75 PB | ... unused hole
106 ffa0000000000000 | -24 PB | ffd1ffffffffffff | 12.5 PB | vmalloc/ioremap space (vmalloc_base)
107 ffd2000000000000 | -11.5 PB | ffd3ffffffffffff | 0.5 PB | ... unused hole
108 ffd4000000000000 | -11 PB | ffd5ffffffffffff | 0.5 PB | virtual memory map (vmemmap_base)
109 ffd6000000000000 | -10.5 PB | ffdeffffffffffff | 2.25 PB | ... unused hole
110 ffdf000000000000 | -8.25 PB | fffffbffffffffff | ~8 PB | KASAN shadow memory
113 … | Identical layout to the 47-bit one from here on:
116 fffffc0000000000 | -4 TB | fffffdffffffffff | 2 TB | ... unused hole
118 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
119 fffffe8000000000 | -1.5 TB | fffffeffffffffff | 0.5 TB | ... unused hole
120 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks
121 ffffff8000000000 | -512 GB | ffffffeeffffffff | 444 GB | ... unused hole
122 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
123 ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | ... unused hole
124 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
125 ffffffff80000000 |-2048 MB | | |
126 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
127 ffffffffff000000 | -16 MB | | |
128 …FIXADDR_START | ~-11 MB | ffffffffff5fffff | ~0.5 MB | kernel-internal fixmap range, variable s…
129 ffffffffff600000 | -10 MB | ffffffffff600fff | 4 kB | legacy vsyscall ABI
130 ffffffffffe00000 | -2 MB | ffffffffffffffff | 2 MB | ... unused hole
133 Architecture defines a 64-bit virtual address. Implementations can support
134 less. Currently supported are 48- and 57-bit virtual addresses. Bits 63
135 through to the most-significant implemented bit are sign extended.
150 Their order is preserved but their base will be offset early at boot time.
153 range must not overlap with anything except the KASAN shadow area, which is
156 For both 4- and 5-level layouts, the STACKLEAK_POISON value in the last 2MB