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

Re: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Thu, 5 Jan 2006 11:01:42 +0100
Delivery-date: Thu, 05 Jan 2006 09:04:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD5902DB1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <516F50407E01324991DD6D07B0531AD5902DB1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Mercredi 04 Janvier 2006 16:55, Magenheimer, Dan (HP Labs Fort Collins) a 
écrit :
> > >If Xen requires virtual_mem_map, then dom0 will require it too.
> > >Since dom0 can't work yet with virtual_mem_map, enabling it
> >
> > in Xen is moot,
> >
> > >isn't it ?
> > >
> > >Tristan.
>
> Yes, I agree.  For virtual_mem_map to work, I think domain0
> needs to be given a granule of physical memory for each "island"
> in the EFI memmap.
I think this is a little bit too kludgy...

> > Seems like that. If we add phys2mach (p!=m) concept into
> > dom0, that's not the issue then. ;-)
>
> True.  But if domain0 owns all of physical memory, its not
> an issue either.  The problem is that the current design
> and implementation of Xen/ia64 management of physical memory
> is half-way between two good solutions.  We will need to
> choose one solution soon.  This should be a good discussion
> at the Xen summit.
I wholy agree with you.

Tristan.


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