x86: remove usage of CONFIG_KERNEL_LINK_IN_VIRT
There is no need to use this kconfig, as the phys-to-virt offset is enough to figure out if the kernel is linked in virtual address space in gen_mmu.py. For code, use Z_VM_KERNEL instead. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
This commit is contained in:
parent
4c7bde4311
commit
273a5e670b
4 changed files with 8 additions and 15 deletions
|
@ -11,12 +11,6 @@
|
|||
* By default, the kernel is linked at its physical address and all addresses
|
||||
* are in RAM.
|
||||
*
|
||||
* If CONFIG_KERNEL_LINK_IN_VIRT is enabled, the kernel is linked at
|
||||
* the virtual address space defined by CONFIG_KERNEL_VM_BASE,
|
||||
* and CONFIG_KERNEL_VM_SIZE. CONFIG_KERNEL_VM_OFFSET defines the offset of
|
||||
* the start of virtual address space to place the kernel. This allows
|
||||
* the kernel to have a bigger address space.
|
||||
*
|
||||
* If CONFIG_XIP is enabled, then another MEMORY region is declared for ROM,
|
||||
* and this is where the Zephyr image is booted from. The linker LMAs and VMAs
|
||||
* are set up, such that read/write data/bss have their VMA addresses
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue