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(-)

-- 
2.17.1