bbf94b0421
commit ef69d2559fe91f23d27a3d6fd640b5641787d22e upstream.
riscv establishes 2 virtual mappings:
- early_pg_dir maps the kernel which allows to discover the system
memory
- swapper_pg_dir installs the final mapping (linear mapping included)
We used to map the dtb in early_pg_dir using DTB_EARLY_BASE_VA, and this
mapping was not carried over in swapper_pg_dir. It happens that
early_init_fdt_scan_reserved_mem() must be called before swapper_pg_dir is
setup otherwise we could allocate reserved memory defined in the dtb.
And this function initializes reserved_mem variable with addresses that
lie in the early_pg_dir dtb mapping: when those addresses are reused
with swapper_pg_dir, this mapping does not exist and then we trap.
The previous "fix" was incorrect as early_init_fdt_scan_reserved_mem()
must be called before swapper_pg_dir is set up otherwise we could
allocate in reserved memory defined in the dtb.
So move the dtb mapping in the fixmap region which is established in
early_pg_dir and handed over to swapper_pg_dir.
This patch had to be backported because:
- the documentation for sv57 is not present here (as sv48/57 are not
present)
- handling of sv48/57 is not needed (as not present)
Fixes: 922b0375fc93 ("riscv: Fix memblock reservation for device tree blob")
Fixes: 8f3a2b4a96dc ("RISC-V: Move DT mapping outof fixmap")
Fixes: 50e63dd8ed92 ("riscv: fix reserved memory setup")
Reported-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/all/f8e67f82-103d-156c-deb0-d6d6e2756f5e@microchip.com/
Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Tested-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20230329081932.79831-2-alexghiti@rivosinc.com
Cc: stable@vger.kernel.org # 5.15.x
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
64 lines
3.5 KiB
ReStructuredText
64 lines
3.5 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
||
|
||
=====================================
|
||
Virtual Memory Layout on RISC-V Linux
|
||
=====================================
|
||
|
||
:Author: Alexandre Ghiti <alex@ghiti.fr>
|
||
:Date: 12 February 2021
|
||
|
||
This document describes the virtual memory layout used by the RISC-V Linux
|
||
Kernel.
|
||
|
||
RISC-V Linux Kernel 32bit
|
||
=========================
|
||
|
||
RISC-V Linux Kernel SV32
|
||
------------------------
|
||
|
||
TODO
|
||
|
||
RISC-V Linux Kernel 64bit
|
||
=========================
|
||
|
||
The RISC-V privileged architecture document states that the 64bit addresses
|
||
"must have bits 63–48 all equal to bit 47, or else a page-fault exception will
|
||
occur.": that splits the virtual address space into 2 halves separated by a very
|
||
big hole, the lower half is where the userspace resides, the upper half is where
|
||
the RISC-V Linux Kernel resides.
|
||
|
||
RISC-V Linux Kernel SV39
|
||
------------------------
|
||
|
||
::
|
||
|
||
========================================================================================================================
|
||
Start addr | Offset | End addr | Size | VM area description
|
||
========================================================================================================================
|
||
| | | |
|
||
0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different per mm
|
||
__________________|____________|__________________|_________|___________________________________________________________
|
||
| | | |
|
||
0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of non-canonical
|
||
| | | | virtual memory addresses up to the -256 GB
|
||
| | | | starting offset of kernel mappings.
|
||
__________________|____________|__________________|_________|___________________________________________________________
|
||
|
|
||
| Kernel-space virtual memory, shared between all processes:
|
||
____________________________________________________________|___________________________________________________________
|
||
| | | |
|
||
ffffffc000000000 | -256 GB | ffffffc7ffffffff | 32 GB | kasan
|
||
ffffffcefea00000 | -196 GB | ffffffcefeffffff | 6 MB | fixmap
|
||
ffffffceff000000 | -196 GB | ffffffceffffffff | 16 MB | PCI io
|
||
ffffffcf00000000 | -196 GB | ffffffcfffffffff | 4 GB | vmemmap
|
||
ffffffd000000000 | -192 GB | ffffffdfffffffff | 64 GB | vmalloc/ioremap space
|
||
ffffffe000000000 | -128 GB | ffffffff7fffffff | 124 GB | direct mapping of all physical memory
|
||
__________________|____________|__________________|_________|____________________________________________________________
|
||
|
|
||
|
|
||
____________________________________________________________|____________________________________________________________
|
||
| | | |
|
||
ffffffff00000000 | -4 GB | ffffffff7fffffff | 2 GB | modules, BPF
|
||
ffffffff80000000 | -2 GB | ffffffffffffffff | 2 GB | kernel
|
||
__________________|____________|__________________|_________|____________________________________________________________
|