1f3ac86b4c
Early in the boot process the memory layout of a pv-domain is changed to match the E820 map (either the host one for Dom0 or the Xen one) regarding placement of RAM and PCI holes. This requires removing memory pages initially located at positions not suitable for RAM and adding them later at higher addresses where no restrictions apply. To be able to operate on the hypervisor supported p2m list until a virtual mapped linear p2m list can be constructed, remapping must be delayed until virtual memory management is initialized, as the initial p2m list can't be extended unlimited at physical memory initialization time due to it's fixed structure. A further advantage is the reduction in complexity and code volume as we don't have to be careful regarding memory restrictions during p2m updates. Signed-off-by: Juergen Gross <jgross@suse.com> Reviewed-by: David Vrabel <david.vrabel@citrix.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com> |
||
|---|---|---|
| .. | ||
| cpuid.h | ||
| events.h | ||
| hypercall.h | ||
| hypervisor.h | ||
| interface.h | ||
| interface_32.h | ||
| interface_64.h | ||
| page-coherent.h | ||
| page.h | ||
| pci.h | ||
| swiotlb-xen.h | ||
| trace_types.h | ||