WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

[Xen-ia64-devel] [PATCH 0/14] memmap: embed memory map in domain pseudo

To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-ia64-devel] [PATCH 0/14] memmap: embed memory map in domain pseudo physical address space
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Thu, 17 May 2007 19:43:56 +0900
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Delivery-date: Thu, 17 May 2007 03:42:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
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.

- 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.

The last patch isn't a part of this improvement, but it is based on
the series of patches and xensource bugzilla id 980 is reported so that
I included it.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=980
NOTE: I tested it only on tiger4. The patch needs test on a machine which
      has large efi memmap.


[PATCH  1/14] memmap: add IA64_DOM0VP_fpswa_revision hypercall for ia64 domain 
builder memmap support
[PATCH  2/14] memmap: introduce memmap_info_t
[PATCH  3/14] memmap: preliminary domain-builder clean up
[PATCH  4/14] memmap: copy dom_fw.c to dom_fw_common.c
[PATCH  5/14] memmap: split dom_fw_common.c into dom0 builder, domu builder and 
utility functions.
[PATCH  6/14] memmap: move pal_call_stub from xenasm.S to dom_fw_asm.S to be 
shared by xen and libxc
[PATCH  7/14] memmap: update Makefile
[PATCH  8/14] memmap: preliminary header file clean up
[PATCH  9/14] memmap: add necessary definitions
[PATCH 10/14] memmap: remove the unused file, xen/arch/ia64/xen/dom_fw.c
[PATCH 11/14] memmap: make libxc domain builder set up firmware instead of xen 
hyperviser
[PATCH 12/14] memmap: ia64 domVTi memmap info support
[PATCH 13/14] memmap: dump-core: enable ia64 memory map code
[PATCH 14/14] memmap: allow huge size efi memory map of real machine

thanks.

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

<Prev in Thread] Current Thread [Next in Thread>