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-devel

Re: [Xen-devel] Re: "Barry Silverman": Setting GDT entries for Thread Lo

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: "Barry Silverman": Setting GDT entries for Thread Local Storage
From: Zachary Amsden <zamsden@xxxxxxxxx>
Date: Tue, 10 Feb 2004 09:49:19 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Tue, 10 Feb 2004 18:18:08 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1AqHEV-0005CD-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: Cisco Systems
References: <E1AqHEV-0005CD-00@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208
Keir Fraser wrote:

I am trying to port the Fedora version of Linux to xeno-linux. It involves
porting the NPTL Library (New Posix Thread Library), and TLS (Thread Local
Storage) kernel changes which Redhat backported from 2.6 into 2.4.

...
This shoudl all work straightforwardly, unless TLS tries to install
segments that are "full size" (i.e. 4GB). I know that one of the
recent glibc threading solutions tries to do this --- it won't work
with Xen because we clip segments so that they do not overlap with
Xen's reserved area in the top 64MB of the virtual address space.
I don't want to throw a monkeywrench in your plans, but another potential trouble spot is the x86 vsyscall interface in 2.6. The vsyscall region sits at the top of the virtual address space, and could conflict with the Xen mapping. You may have to consider remapping Xen to another memory region, but I'm not sure where there may be other trouble areas with Windows domains (map?). At some point in the forseeable future, it might no longer be possible to locate Xen at an OS neutral location, so perhaps it is worth considering the remapping problem now.

Zachary Amsden
zamsden@xxxxxxxxx


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel