[Xen-ia64-devel] [RFC][PATCH 0/10] memmap: embed memory map in domain pseudo physical address space

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

Hi all.

Xen/IA64 XEN_DOMCTL_arch_setup hypercall needs flexibility
to address the following issues.
- xm dump-core/save/restore.
  Such utilities need to know the area where memory is populated.
  Currently domU populates memory dense, but this wouldn't be
  true in future.
  Especially VTi domain builder populate memory sparsely so that
  xm dump-core/save/restore doesn't work for domVTi without the predefined 
  knowledge of memory layout.
- sparse populated domU for driver domain or other purpose(e.g. NUMA)
  The domain builder needs flexibility to populate memory sparsely.

I send out the experimental patch before and Tristan pointed out
that domain firmware builder should be in libxc.

Although This patch isn't finished yet (fpswa isn't supported yet.),
the patches become much larger than I expected.
So I want to hear ideas before completing it.


- creates memory map as efi runtime data in domain pseudo
  physical space,
- adds new member, memmap_info_num_pages, memmap_info_pfn, to
  struct arch_shared_info
- set memmap_info_pfn to point memory map
- modifies XEN_DOMCTL_arch_setup so that it create EFI memory descriptor
  following the specified memory map.
  It abuses xen_ia64_boot_param to pass memory map.
- move domain builder functionalities from xen to libxc.

thanks.

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel