|
@@ -19,7 +19,7 @@ ffffff0000000000 - ffffff7fffffffff (=39 bits) %esp fixup stacks
|
|
|
ffffffef00000000 - fffffffeffffffff (=64 GB) EFI region mapping space
|
|
|
... unused hole ...
|
|
|
ffffffff80000000 - ffffffff9fffffff (=512 MB) kernel text mapping, from phys 0
|
|
|
-ffffffffa0000000 - ffffffffff5fffff (=1526 MB) module mapping space
|
|
|
+ffffffffa0000000 - ffffffffff5fffff (=1526 MB) module mapping space (variable)
|
|
|
ffffffffff600000 - ffffffffffdfffff (=8 MB) vsyscalls
|
|
|
ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
|
|
|
|
|
@@ -39,6 +39,9 @@ memory window (this size is arbitrary, it can be raised later if needed).
|
|
|
The mappings are not part of any other kernel PGD and are only available
|
|
|
during EFI runtime calls.
|
|
|
|
|
|
+The module mapping space size changes based on the CONFIG requirements for the
|
|
|
+following fixmap section.
|
|
|
+
|
|
|
Note that if CONFIG_RANDOMIZE_MEMORY is enabled, the direct mapping of all
|
|
|
physical memory, vmalloc/ioremap space and virtual memory map are randomized.
|
|
|
Their order is preserved but their base will be offset early at boot time.
|