From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 24 16:49:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE2916A598; Mon, 24 Jul 2006 16:49:27 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2331C43D53; Mon, 24 Jul 2006 16:49:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k6OGnPBx017909; Mon, 24 Jul 2006 12:49:25 -0400 (EDT) Date: Mon, 24 Jul 2006 12:49:25 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Tijl Coosemans In-Reply-To: <200607241839.28229.tijl@ulyssis.org> Message-ID: References: <200607221914.15826.lofi@freebsd.org> <200607241706.08396.tijl@ulyssis.org> <200607241839.28229.tijl@ulyssis.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org, Michael Nottebrock Subject: Re: WINE vs. FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 16:49:27 -0000 On Mon, 24 Jul 2006, Tijl Coosemans wrote: > On Monday 24 July 2006 17:39, Daniel Eischen wrote: >> On Mon, 24 Jul 2006, Tijl Coosemans wrote: >>> I've attached two patches that accomplish this, but this seems to >>> trigger other problems, so use at your own risk. If you want to try >>> them, place them in the port's files/ directory and add a line >>> containing "USE_AUTOTOOLS= autoconf:259" to the Makefile. This >>> seems to break wine+libpthread, so I've also changed the port to >>> use libthr instead. >>> >>> For the libpthread experts, I haven't investigated that much >>> further yet, but libpthread seems to fail in create_stack() from >>> _pthread_create() from _thr_start_sig_daemon(). >> >> See my response to this in a previous reply to this thread. libthr >> and libpthread use LDT's for TLS. WINE is stomping on them because >> it doesn't properly create LDTs. This is not a problem with either >> of the thread libraries and this issue has been known ever since we >> implemented TLS years ago. > > And as I stated later on in that thread, I don't see where libpthread > and libthr still use LDT entries. As far as I understand the code, > instead of using an LDT entry per thread (as it sure used to be), only > one single GDT entry is used whose base address is updated during a > context switch. Looking at the cvs history, it has been working like > this since a couple commits of Peter Wemm about a year ago. > > And if nothing but Wine uses the LDT, Wine's static allocation of LDT > entries can't be the problem. Look, we use %gs for TLS, period. Go see libpthread/arch/i386/i386/pthread_md.c for how libpthread does it. TLS would not work without setting aside a register for the threads library (and rtld) to use. -- DE