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/
Home Products Support Community News


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

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 5 Jan 2006 08:21:03 -0800
Delivery-date: Thu, 05 Jan 2006 16:26:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Thread-topic: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix
Committed.  Sorry for the delay. 

> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx] 
> Sent: Wednesday, January 04, 2006 5:54 PM
> To: Magenheimer, Dan (HP Labs Fort Collins); Tristan Gingold; 
> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] [PATCH] Another important 
> Xen/ia64 domU/vbd fix
> >From: Magenheimer, Dan (HP Labs Fort Collins) 
> [mailto:dan.magenheimer@xxxxxx]
> >Sent: 2006年1月4日 23:55
> >
> >> >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.
> >
> >> 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.
> >
> >Dan
> Yes, we will discuss at summit. In the meantime, please give 
> this patch a check-in since it's critical to make IA64/DOMU 
> working for boxes with larger memory configuration.
> Thanks,
> Kevin
Xen-ia64-devel mailing list