Hi Henry,
On 08/09/2022 12:09, Henry Wang wrote:
> The static heap, or statically configured heap, refers to parts
> of RAM reserved in the beginning for heap. Like the static memory
> allocation, such static heap regions are reserved by configuration
> in the device tree using physical address ranges.
>
> 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 heap.
>
> The first patch enhances the error handling in processing the dts
> chosen node. The second patch introduces the static heap and the
> device tree parsing code. The third patch renames xenheap_* to
> directmap_* for better readablity. The fourth patch adds the
> implementation of the static heap pages handling in boot and heap
> allocator for Arm.
>
> Changes from v5 to v6:
> - Refine doc.
> - Drop duplicated code.
> - Add Julien's Reviewed-by.
>
> Henry Wang (4):
> xen/arm: bootfdt: Make process_chosen_node() return int
> docs, xen/arm: Introduce static heap memory
> xen/arm: mm: Rename xenheap_* variable to directmap_*
> xen/arm: Handle static heap pages in boot and heap allocator
I have now committed the series. This required a small tweak in
booting.txt because I merged it after Rahul event channel's series which
also modifies booting.txt.
Cheers,
--
Julien Grall