From e211d3a99900ed87c8f171fae5c983433347c75a Mon Sep 17 00:00:00 2001 From: Daniel Leung Date: Sat, 6 Mar 2021 20:36:36 -0800 Subject: [PATCH] kernel: remove CONFIG_KERNEL_LINK_IN_VIRT There actually is no need for a separate kconfig here, as the kernel VM address and SRAM address can be used to figure out if the kernel is linked in virtual address space. Signed-off-by: Daniel Leung --- Kconfig.zephyr | 17 ----------------- arch/Kconfig | 1 - 2 files changed, 18 deletions(-) diff --git a/Kconfig.zephyr b/Kconfig.zephyr index 97d24c82958..09840d9b0b2 100644 --- a/Kconfig.zephyr +++ b/Kconfig.zephyr @@ -183,23 +183,6 @@ config SRAM_OFFSET If unsure, leave at the default value 0. -config CAN_LINK_IN_VIRT - bool - help - Hidden option to indicate that the architecture, SoC or board - linker script can link the kernel in virtual address space. - -config KERNEL_LINK_IN_VIRT - bool "Link Kernel in Virtual Address Space" - depends on MMU - depends on CAN_LINK_IN_VIRT - help - Enable linking the kernel in virtual address space defined by - KERNEL_VM_BASE, KERNEL_VM_SIZE and KERNEL_VM_OFFSET. - - Requires linker script support. If unsure, says N and the kernel - will be linked in physical address space. - endmenu menu "Compiler Options" diff --git a/arch/Kconfig b/arch/Kconfig index febe47fdf65..efce310afbd 100644 --- a/arch/Kconfig +++ b/arch/Kconfig @@ -62,7 +62,6 @@ config X86 select ARCH_HAS_TIMING_FUNCTIONS select ARCH_HAS_THREAD_LOCAL_STORAGE select ARCH_HAS_DEMAND_PAGING - select CAN_LINK_IN_VIRT help x86 architecture