On Sat, Apr 07, 2007 at 01:17:34AM +0200, Tristan Gingold wrote:
> > 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.
> The patch doesn't address VTi yet, does it?
> I am interested in seeing how you will manage VTi :-)
I was encouraged so that I was able to complete it.
Although I don't expect those are included in xen 3.0.5,
I attached the left patches for those who are interested in.
Now the next target is save/restore.
The save/restore related bugs (942, 943, 944, 945) are reported, though.
--
yamahata
14775_e9b79736d082_ia64_dom0vp_fpswa_revision_hypercall.patch
Description: Text Data
14776_c80170131617_xen_ia64_fpswa_revision_hypercall.patch
Description: Text Data
14777_b6d6ea871b0b_lock_pages_unlock_pages.patch
Description: Text Data
14778_5600c9749220_ia64_dom_vti_memmap_info_support.patch
Description: Text Data
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
| 
Home