mm.txt 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. Virtual memory map with 4 level page tables:
  2. 0000000000000000 - 00007fffffffffff (=47 bits) user space, different per mm
  3. hole caused by [47:63] sign extension
  4. ffff800000000000 - ffff87ffffffffff (=43 bits) guard hole, reserved for hypervisor
  5. ffff880000000000 - ffff887fffffffff (=39 bits) LDT remap for PTI
  6. ffff888000000000 - ffffc87fffffffff (=64 TB) direct mapping of all phys. memory
  7. ffffc88000000000 - ffffc8ffffffffff (=39 bits) hole
  8. ffffc90000000000 - ffffe8ffffffffff (=45 bits) vmalloc/ioremap space
  9. ffffe90000000000 - ffffe9ffffffffff (=40 bits) hole
  10. ffffea0000000000 - ffffeaffffffffff (=40 bits) virtual memory map (1TB)
  11. ... unused hole ...
  12. ffffec0000000000 - fffffbffffffffff (=44 bits) kasan shadow memory (16TB)
  13. ... unused hole ...
  14. vaddr_end for KASLR
  15. fffffe0000000000 - fffffe7fffffffff (=39 bits) cpu_entry_area mapping
  16. fffffe8000000000 - fffffeffffffffff (=39 bits) LDT remap for PTI
  17. ffffff0000000000 - ffffff7fffffffff (=39 bits) %esp fixup stacks
  18. ... unused hole ...
  19. ffffffef00000000 - fffffffeffffffff (=64 GB) EFI region mapping space
  20. ... unused hole ...
  21. ffffffff80000000 - ffffffff9fffffff (=512 MB) kernel text mapping, from phys 0
  22. ffffffffa0000000 - fffffffffeffffff (1520 MB) module mapping space
  23. [fixmap start] - ffffffffff5fffff kernel-internal fixmap range
  24. ffffffffff600000 - ffffffffff600fff (=4 kB) legacy vsyscall ABI
  25. ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
  26. Virtual memory map with 5 level page tables:
  27. 0000000000000000 - 00ffffffffffffff (=56 bits) user space, different per mm
  28. hole caused by [56:63] sign extension
  29. ff00000000000000 - ff0fffffffffffff (=52 bits) guard hole, reserved for hypervisor
  30. ff10000000000000 - ff10ffffffffffff (=48 bits) LDT remap for PTI
  31. ff11000000000000 - ff90ffffffffffff (=55 bits) direct mapping of all phys. memory
  32. ff91000000000000 - ff9fffffffffffff (=3840 TB) hole
  33. ffa0000000000000 - ffd1ffffffffffff (=54 bits) vmalloc/ioremap space (12800 TB)
  34. ffd2000000000000 - ffd3ffffffffffff (=49 bits) hole
  35. ffd4000000000000 - ffd5ffffffffffff (=49 bits) virtual memory map (512TB)
  36. ... unused hole ...
  37. ffdf000000000000 - fffffc0000000000 (=53 bits) kasan shadow memory (8PB)
  38. ... unused hole ...
  39. vaddr_end for KASLR
  40. fffffe0000000000 - fffffe7fffffffff (=39 bits) cpu_entry_area mapping
  41. ... unused hole ...
  42. ffffff0000000000 - ffffff7fffffffff (=39 bits) %esp fixup stacks
  43. ... unused hole ...
  44. ffffffef00000000 - fffffffeffffffff (=64 GB) EFI region mapping space
  45. ... unused hole ...
  46. ffffffff80000000 - ffffffff9fffffff (=512 MB) kernel text mapping, from phys 0
  47. ffffffffa0000000 - fffffffffeffffff (1520 MB) module mapping space
  48. [fixmap start] - ffffffffff5fffff kernel-internal fixmap range
  49. ffffffffff600000 - ffffffffff600fff (=4 kB) legacy vsyscall ABI
  50. ffffffffffe00000 - ffffffffffffffff (=2 MB) unused hole
  51. Architecture defines a 64-bit virtual address. Implementations can support
  52. less. Currently supported are 48- and 57-bit virtual addresses. Bits 63
  53. through to the most-significant implemented bit are sign extended.
  54. This causes hole between user space and kernel addresses if you interpret them
  55. as unsigned.
  56. The direct mapping covers all memory in the system up to the highest
  57. memory address (this means in some cases it can also include PCI memory
  58. holes).
  59. vmalloc space is lazily synchronized into the different PML4/PML5 pages of
  60. the processes using the page fault handler, with init_top_pgt as
  61. reference.
  62. We map EFI runtime services in the 'efi_pgd' PGD in a 64Gb large virtual
  63. memory window (this size is arbitrary, it can be raised later if needed).
  64. The mappings are not part of any other kernel PGD and are only available
  65. during EFI runtime calls.
  66. Note that if CONFIG_RANDOMIZE_MEMORY is enabled, the direct mapping of all
  67. physical memory, vmalloc/ioremap space and virtual memory map are randomized.
  68. Their order is preserved but their base will be offset early at boot time.
  69. Be very careful vs. KASLR when changing anything here. The KASLR address
  70. range must not overlap with anything except the KASAN shadow area, which is
  71. correct as KASAN disables KASLR.