Re: [Xen-ia64-devel] [PATCH][RFC] embed memory map in domain pseudo physical address space

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

On Fri, Feb 02, 2007 at 06:42:28AM +0100, Tristan Gingold wrote:
> On Thu, Feb 01, 2007 at 10:15:21PM +0900, Isaku Yamahata wrote:
> > Hi all.
> > 
> > Xen/IA64 XEN_DOMCTL_arch_setup hypercall needs flexibilty
> > to address the following issues.
> > - xm dump-core. (save/restore would use in near future)
> >   Now I'm trying to enhance xm dump-core for IA64.
> >   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 spasely so that
> >   xm dump-core doesn't work for domVTi.
> > - sparse populated domU for driver domain or other purose(e.g. NUMA)
> >   The domain builder needs flexibility to populate memory sparsely.
> Hi,
> 
> I agree with the goal.
> Although I don't have all the details in memory, why not fully build the
> domain (ie building pal/sal stubs) from libxc ?

It makes much sense.


> If this is doable, I think it should be cleaner.

I think it's feasible and it makes arch_setup hypercall less functional.


> [This is just an idea to be discussed.  If we agree this is cleaner and doable
> then someone might implement it. The only drawback might be code duplication]

We can clean the code up to share between hypervisor and libxc
using symbolic link.

-- 
yamahata

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