[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [RFC PATCH 0/2] Introduce reserved Xenheap
Hi Henry, On 24/02/2022 01:30, Henry Wang wrote: The reserved Xenheap, or statically configured Xenheap, refers to parts of RAM reserved in the beginning for Xenheap. Like the static memory allocation, such reserved Xenheap regions are reserved by configuration in the device tree using physical address ranges. In Xen, we have the concept of domheap and xenheap. For Arm64 and x86 they would be the same. But for Arm32, they would be different: xenheap is always mapped whereas domheap is separate. Skimming through the series, I think you want to use the region for both domheap and xenheap. Is that correct? Furthemore, now that we are introducing more static region, it will get easier to overlap the regions by mistakes. I think we want to have some logic in Xen (or outside) to ensure that none of them overlaps. Do you have any plan for that? This feature is useful to run Xen on Arm MPU systems, where only a finite number of memory protection regions are available. The limited number of protection regions places requirement on planning the use of MPU protection regions and one or more MPU protection regions needs to be reserved only for Xenheap. Therefore, this patch series is sent as RFC for comments from the community. The first patch introduces the reserved Xenheap and the device tree processing code. The second patch adds the implementation of the reserved Xenheap pages handling in boot and heap allocator on Arm64. Henry Wang (2): docs, xen/arm: Introduce reserved Xenheap memory xen/arm: Handle reserved Xenheap pages in boot/heap allocator docs/misc/arm/device-tree/booting.txt | 43 ++++++++++++++++++++++ xen/arch/arm/bootfdt.c | 52 +++++++++++++++++++++------ xen/arch/arm/include/asm/setup.h | 3 ++ xen/arch/arm/setup.c | 52 +++++++++++++++++++-------- 4 files changed, 125 insertions(+), 25 deletions(-) -- Julien Grall
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |