Hi Penny,
On 26/06/2023 04:33, Penny Zheng wrote:
CAUTION: This message has originated from an External Source. Please use proper
judgment and caution when opening attachments, clicking links, or responding to
this email.
This commit wants to introduce a new Kconfig CONFIG_HAS_MMU to guard
MMU-related codes, to tell two different memory management architecture:
VMAS and PMSA.
In a VMSA system, a Memory Management Unit (MMU) provides fine-grained
control of a memory system through a set of virtual to physical address
mappings and associated memory properties held in memory-mapped tables
known as translation tables.
Signed-off-by: Penny Zheng <penny.zh...@arm.com>
Signed-off-by: Wei Chen <wei.c...@arm.com>
---
v3:
- new patch
---
xen/arch/arm/Kconfig | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/xen/arch/arm/Kconfig b/xen/arch/arm/Kconfig
index ff17345cdb..fb77392b82 100644
--- a/xen/arch/arm/Kconfig
+++ b/xen/arch/arm/Kconfig
@@ -60,6 +60,14 @@ config PADDR_BITS
source "arch/Kconfig"
+config HAS_MMU
+ bool "Memory Management Unit support in a VMSA system"
+ default y
+ help
+ In a VMSA system, a Memory Management Unit (MMU) provides
fine-grained control of
+ a memory system through a set of virtual to physical address mappings
and associated memory
+ properties held in memory-mapped tables known as translation tables.
+
config ACPI
bool "ACPI (Advanced Configuration and Power Interface) Support
(UNSUPPORTED)" if UNSUPPORTED
depends on ARM_64
I don't think you need this option.
In patch 52 ("xen/arm: add Kconfig option CONFIG_HAS_MPU to enable MPU
system support"), you have introduced "HAS_MPU" option.
May be you can introduce "HAS_MPU" option a bit earlier, so that
"!HAS_MPU" is "HAS_MMU". So, you will not need this new option.
Let me know if this makes sense.
- Ayan
--
2.25.1
