Skip to content

Static heap follow-up doc changes

Henry Wang xen-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 10 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2docs: Document the minimal requirement of static heapdocs/misc/arm/device-tree/booting.txt+7 -07 replies
2/2SUPPORT.md: Mark static heap feature as supportedSUPPORT.md+1 -13 replies

Reviews trailers per patch

1 of 2 patches has a Reviewed-by or Acked-by.

PatchStefano Stabellini
1/2A-b
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH for-4.17 0/2] Static heap follow-up doc changes

The static heap feature requires user to know the minimal size of heap to make sure the system can work. Since the heap controlled by Xen is intended to provide memory for the whole system, not only the boot time memory allocation should be covered by the static heap region, but also the runtime allocation should be covered.

The main source of runtime allocation is the memory for the P2M. Currently, from XSA-409, the P2M memory is bounded by the P2M pool. So make this part as the minimal requirement of static heap. The amount of memory allocated after all the guests have been created should be quite limited and mostly predictable.

Also, with the P2M pages pool bounding the domain memory runtime allocation and the documented minimal size requirement of the static heap, it is safe to mark static heap feature as supported.

This series handles the above-mentioned doc changes respectively.

Henry Wang (2):
docs: Document the minimal requirement of static heap SUPPORT.md: Mark static heap feature as supported

 SUPPORT.md                            | 2 +-
 docs/misc/arm/device-tree/booting.txt | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)
Signature · 1 line
2.17.1