portugalfuturista/seL4
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

RISC-V: Comment 64-bit SV39 kernel address space

Browse source 
Add a comment and diagram explaining the current structure of the SV39
kernel address space. The top half of the virtual address space is
reserved for the kernel and consists of the Kernel window of all
accessible physical memory, the kernel ELF mapping and the Kernel device
mapping region.
This commit is contained in:
Kent McLeod 2019-05-22 19:35:36 +10:00
parent 10655ce634
commit 4957c5e8a5
1 changed files with 61 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

67
include/plat/spike/plat/64/plat_mode/machine/hardware.h
View file

@ -15,13 +15,68 @@
#include <config.h>
#if CONFIG_PT_LEVELS == 3
/* The top half of the address space is reserved for the kernel. This means that 256 top level
* entires are for the user, and 256 are for the kernel. This will be further split into the
* 'regular' kernel window, which contains mappings to physical memory, and a small higher
* kernel image window that we use for running the actual kernel from */
/* We steal the top 2 gb entries for the kernel, this means that between PPTR_BASE and
/*
* The top half of the address space is reserved for the kernel. This means that 256 top level
* entries are for the user, and 256 are for the kernel. This will be further split into the
* 'regular' kernel window, which contains mappings to physical memory, a small (1GiB) higher
* kernel image window that we use for running the actual kernel from and a top 1GiB window for
* kernel device mappings. This means that between PPTR_BASE and
* KERNEL_BASE there are 254 entries remaining, which represents how much physical memory
* can be used */
* can be used.
*
* Almost all of the top 256 kernel entries will contain 1GiB page mappings. The only 2 entries
* that contain a 2nd level PageTable consisting of 2MiB page entries is the entry
* for the 1GiB Kernel ELF region and the 1GiB region corresponding to the physical memory
* of the kernel ELF in the kernel window. The same 2nd level PageTable is used and so both
* entries refer to the same 1GiB of physical memory.
* This means that the 1GiB kernel ELF mapping will correspond to physical memory with a 1GiB
* alignment.
*
* +-----------------------------+ 2^64
* | Kernel Devices |
* -> +-------------------PPTR_KDEV-+ 2^64 - 1GiB
* | | Kernel ELF |
* ----| +-------------KERNEL_ELF_BASE-+ --+ 2^64 - 2GiB + (PADDR_LOAD % 1GiB)
* | | | |
* | -> +-----------------KERNEL_BASE-+ --+ 2^64 - 2GiB
* Shared 1GiB| | | |
* table entry| | PSpace | |
* | | (direct kernel mappings) | +----+
* ------>| | | |
* | | | |
* +-------------------PPTR_BASE-+ --+ 2^64 - 2^c
* | | | +-------------------------+
* | | | | |
* | | | | |
* | Invalid | | | |
* | | | | not |
* | | | | kernel |
* | | | | addressable |
* +-----------------------------+ 2^c | | |
* | | | | |
* | | | | |
* | | | +- --------------------------+ PADDR_TOP =
* | | | | | | KERNEL_BASE - PPTR_BASE
* | | | | | |
* | | | | | |
* | User | | | | |
* | | | | | |
* | | +------+ +-------------------------+ PADDR_HIGH_TOP =
* | | kernel | | Kernel ELF | (PPTR_KDEV - KERNEL_ELF_BASE + PADDR_LOAD)
* | | addressable | +-------------------------+ PADDR_LOAD
* | | | | |
* | | | | |
* +-----------------------------+ 0 +- +-------------------------+ 0 PADDR_BASE
*
* virtual address space physical address space
*
*
* c = one less than number of bits the page tables can translate
* = sign extension bit for canonical addresses
* (= 47 on x64, 38 on RISCV64 sv39, 47 on RISCV64 sv48)
*
*/
/* This is the base of the kernel window, which is directly mapped to PADDR_BASE */
#define PPTR_BASE 0xFFFFFFC000000000lu