From owner-freebsd-emulation@FreeBSD.ORG Mon Jan 22 22:11:59 2007 Return-Path: X-Original-To: freebsd-emulation@freebsd.org Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46D4616A402; Mon, 22 Jan 2007 22:11:59 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id C159513C4A7; Mon, 22 Jan 2007 22:11:58 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0MMBvUj057974 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 23:11:57 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0MMBvBI057973; Mon, 22 Jan 2007 23:11:57 +0100 (CET) Date: Mon, 22 Jan 2007 23:11:57 +0100 From: Divacky Roman To: Tijl Coosemans Message-ID: <20070122221157.GA54796@stud.fit.vutbr.cz> References: <790a9fff0701211041j1176d00gd6dd75d0989cf4ec@mail.gmail.com> <200701220001.22404.tijl@ulyssis.org> <20070122081810.GA42976@stud.fit.vutbr.cz> <200701221752.21628.tijl@ulyssis.org> <20070122212624.GA49466@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070122212624.GA49466@stud.fit.vutbr.cz> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: freebsd-emulation@freebsd.org, jkim@freebsd.org Subject: Re: linuxolator: tls_test results amd64 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 22:11:59 -0000 > overall you are saying that to support linux32 tls we have to > > 1) load an unused segment with proper values > 2) return the number of the segment from the set_thread_syscall > 3) make the automatic loading/unloading of that segment to happen on > every context switch (just like its done for segment 3 on i386) rethought it a little and I think I understand now... I think simple reloading the segment thats used for TLS (which one is it?) on fbsd@amd64 should do the trick. what do you think? so instead of rewriting just the base address we reload the whole segment. that should not be that hard. but I dont understand the connection between fs/gs and the segment. is it that reloading fs_base resets the base in the segment the fs points at? roman