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] Re: [Xen-devel] [PATCH 0/5] dump-core take 2:

On Thu, Jan 18, 2007 at 04:54:05PM +0800, Tian, Kevin wrote:
> Yeah, memory map may be sparse on ia64, but, only at physical level. 
> You can always present a compact pseudo physical layout to a 
> domain, despite of sparse or not in real physical.:-) 

That's right. Xen/ia64 does so now for paravirtualized domain 
except dom0.
There is an unsolved issue. If much memory (e.g. >4GB) is given
to a driver domain, the domain can't access I/O.
At least the I/O area must be avoided somehow,
thus paravirtualized domain's memory map may become sparse
(in the future when the issue is solved).

> BTW, is it possible 
> to save memmap into xenstore, so that multiple user components can 
> communicate such info directly without xen's intervention?

Do you have any usage in mind?


Xen-devel mailing list