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] Virtual mem map

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Virtual mem map
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Mon, 9 Jan 2006 11:49:48 +0100
Delivery-date: Mon, 09 Jan 2006 10:25:27 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD5902F85@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: <516F50407E01324991DD6D07B0531AD5902F85@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Vendredi 06 Janvier 2006 22:40, Magenheimer, Dan (HP Labs Fort Collins) a 
écrit :
> > I am currently thinking about virtual mem map.
> > In Linux, the virtual mem map is (surprise) virtually mapped.
> > In Xen, we can use the same approach or we can manually cut
> > the mem map into
> > several pieces using a mechanism similar to paging.
[...]
> I think you will need to explain a little bit more what you
> mean by "a mechanism similar to paging" before it will
> be possible to comment.  Paging, to me, means there is some
> kind of swap drive or backing store to allow more "virtual"
> pages than "physical" pages.
[I have just describe it in my previous mail].

> I spent a lot of time recently digging through the physical
> memory management code of Linux/ia64.  It is very messy because
> it has to support a wide variety of physical memory layouts.
> And it makes surprising choices that throw away huge chunks of
> physical memory (anything that doesn't fit conveniently in
> a "granule").
Yes, this is very surprising.  At least 16MB of memory are lost!  Maybe Xen 
can use this memory for itself ?

>  Getting this all working on multiple machines
> will probably be a big challenge.  It might be best to use
> Linux code that is known to work on many machines.
Sure.
On the other side, Xen (almost) don't use ptc/itc for itself.  

> I agree with your concern though that taking TLB misses when
> looking up a page struct in Xen is likely to cause performance
> problems and some difficult bugs.  It might be worthwhile to
> put some counters in to see how frequently the memmap is
> accessed and code some defensive bounds checks to ensure
> wild accesses are immediately flagged with a BUG rather than
> resulting in random memory accesses.
I agree.
Tristan.


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

<Prev in Thread] Current Thread [Next in Thread>